3 ms·
> Unless the company is doing something that requires almost no special domain knowledge, it's almost inevitable that it's going to take a good while for them t
by deaux 1y ago
> Unless the company is doing something that requires almost no special domain knowledge, it's almost inevitable that it's going to take a good while for them to on-board. For us, it usually takes about year to get them to the point that they can contribute without some form of handholding.
I know that such places exist from reading HN but it always seems so counterproductive to join such a place as a fresh grad. As a beginner you need to be getting your hands dirty, getting some ownership and respobsibilities, making mistakes and decisions. Figuring stuff out, exploring tradeoffs and experiencing them firsthand.
It's like when a football player joins a big team before they're ready and spends a year or 2 on the bench. It completely stunts their development and they never reach their potential. When you look at those who reach the top, they were all playing nearly every match from a young age as an important member of their team.
Obviously I'm biased due to personal experience, as everyone is. And there naturally must be upsides to joining your company as a first job as well. But I'm very glad that in my first job I was writing production code and doing both brownfield as well as greenfield stuff by week 2.
- tonyedgecombe 1y ago>But I'm very glad that in my first job I was writing production code and doing both brownfield as well as greenfield stuff by week 2. If you can get up to speed in two weeks then you can be replaced that quickly as well. Getting to know how the business works can be as valuable as CS knowledge.