2 ms·
My rule of thumb: happy programmer = productive programmer productive programmer = happy programmer Lots of managers somewhat assume that a developer is tryi
by muzani 7y ago
My rule of thumb:
happy programmer = productive programmer
productive programmer = happy programmer
Lots of managers somewhat assume that a developer is trying to do as little as possible, but it's quite the opposite. Many have pride in their work, and enjoy getting into flow.
Very often they can get frustrated, with processes, with equipment, and often with themselves.
Sometimes they end up in an unproductivity-depression spiral too, and need a little help out of that. Often the best solution here is not to be hard on them when things go slow, and make it clear that they're encouraged to bring up problems as it happens.
The easiest way to find out is to just listen - regularly schedule 1-on-1s. Well, if you have one programmer, there's going to be a lot of 1 on 1, but keep it a habit.
I'd say don't worry too much about onboarding.
Start them off with a little goal, that's not too time dependent and have someone they can fully interrupt in the first few days. The process of the tech team can change very rapidly in just a few months, based on team size, managers, DevOps, etc.