Skip to main content
edited body
Source Link
Michael
  • 1.2k
  • 10
  • 13

Yet another problem (in addition to those others have pointed out) why this is a bad idea: As an experienced employee you’ll tend to underestimate how hard work is for a new employee is. They don’t know the tools, people, workflow, project history …

A task which takes you one day can easily take a new employee a whole week. First they might not know where the files are located, then they might not have permissions to access them, might not know your IDE, might not know how to debug failing integration checks, might not know whom to contact to resolve any of those issues …

There is a reason why hiring and training new employees is expensive. Don’t even expect productive work within the first 30 days.

Yet another problem (in addition to those others have pointed out) why this is a bad idea: As an experienced employee you’ll tend to underestimate how hard work for a new employee is. They don’t know the tools, people, workflow, project history …

A task which takes you one day can easily take a new employee a whole week. First they might not know where the files are located, then they might not have permissions to access them, might not know your IDE, might not know how to debug failing integration checks, might not know whom to contact to resolve any of those issues …

There is a reason why hiring and training new employees is expensive. Don’t even expect productive work within the first 30 days.

Yet another problem (in addition to those others have pointed out) why this is a bad idea: As an experienced employee you’ll tend to underestimate how hard work is for a new employee. They don’t know the tools, people, workflow, project history …

A task which takes you one day can easily take a new employee a whole week. First they might not know where the files are located, then they might not have permissions to access them, might not know your IDE, might not know how to debug failing integration checks, might not know whom to contact to resolve any of those issues …

There is a reason why hiring and training new employees is expensive. Don’t even expect productive work within the first 30 days.

Source Link
Michael
  • 1.2k
  • 10
  • 13

Yet another problem (in addition to those others have pointed out) why this is a bad idea: As an experienced employee you’ll tend to underestimate how hard work for a new employee is. They don’t know the tools, people, workflow, project history …

A task which takes you one day can easily take a new employee a whole week. First they might not know where the files are located, then they might not have permissions to access them, might not know your IDE, might not know how to debug failing integration checks, might not know whom to contact to resolve any of those issues …

There is a reason why hiring and training new employees is expensive. Don’t even expect productive work within the first 30 days.