Great article. One thing I try to keep in mind with Juniors is career development. I want to expose them to as many diverse learning opportunities as possible while they're working for me for the benefit of them as an individual. I try to make sure they learn about things they might not be personally responsible for, like architecture, DevOps, infrastructure, etc. Not only does it make them more well rounded developers but it boosts their skills for their next position.
Let's face it, most of them won't retire working for you. Giving them this type of exposure not only benefits them while they work for (or with) you but also prepares them for success in the rest of their career.
It's the old adage - "what if we train them and they leave? What if we don't and they stay?"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article. One thing I try to keep in mind with Juniors is career development. I want to expose them to as many diverse learning opportunities as possible while they're working for me for the benefit of them as an individual. I try to make sure they learn about things they might not be personally responsible for, like architecture, DevOps, infrastructure, etc. Not only does it make them more well rounded developers but it boosts their skills for their next position.
Let's face it, most of them won't retire working for you. Giving them this type of exposure not only benefits them while they work for (or with) you but also prepares them for success in the rest of their career.
It's the old adage - "what if we train them and they leave? What if we don't and they stay?"