| 1 |
On 02/16/2011 07:22 PM, Patrick Lauer wrote: |
| 2 |
> On 02/16/11 17:50, Petteri Räty wrote: |
| 3 |
>> Currently the recruiting team handles returning developers in the same |
| 4 |
>> way as people joining the first time. The question that I have been |
| 5 |
>> presented with is if they should get priority? |
| 6 |
> |
| 7 |
> My opinion is that yes, they should be prioritized. They have, in the |
| 8 |
> past, already shown that they do know the relevant things, and if they |
| 9 |
> wish to return we should make it easy for them. |
| 10 |
> |
| 11 |
>> The reasoning being that |
| 12 |
>> in their case it's more about making sure their skills are updated than |
| 13 |
>> making sure they won't cause problems etc. Ideally of course we could |
| 14 |
>> process everyone quickly enough that this wouldn't be a problem but |
| 15 |
>> history has proved this to be challenging to say the least. |
| 16 |
> That is another issue - recruiting is a difficult and slow process. What |
| 17 |
> can we do to make it work better? |
| 18 |
> |
| 19 |
|
| 20 |
I am hoping to get the web application (pending on infra) live and see |
| 21 |
how much that helps but let's keep this thread on the main topic. Please |
| 22 |
start a new thread for a more general discussion if you think it's |
| 23 |
warranted. |
| 24 |
|
| 25 |
Regards, |
| 26 |
Petteri |
Archives