News for hackers. Stuff that matters.
Re:Write Junior Code by nine_k on Sunday December 29, 2019 @08:57PM (#21910128)
Not hiring junior developers makes sense when you are still unfolding, and have a really small engineering team (< 5-7 people).

As you grow, you will see that not all work is equally important, and you want your more senior guys work on harder problems. And you will also note a number of good, smart developers applying to you who do not yet have the experience of a senior engineer, but could quickly grow.

Then you can start hiring junior engineers, and nurture them.

[Edit: grammar]

Re:Write Junior Code by nicoburns on Sunday December 29, 2019 @09:59PM (#21910428)
I'm currently working for a company whose first 4 technical hires (other than the CTO, who wasn't always involved in day-to-day development) were juniors. This was a terrible idea, as there are basic architectural mistakes baked into the codebase all over the place, and lots of issues with data integrity and things that only work most of the time. They'd have been better off with a single senior.

Agree that it makes sense to hire juniors once you've grown though.