3 ms·
It's interesting to focus in specifically on that one when "so far we rely on devs to have a lot of independence and domain knowledge" suggests there isn't the
by JansjoFromIkea 2y ago
It's interesting to focus in specifically on that one when "so far we rely on devs to have a lot of independence and domain knowledge" suggests there isn't the capacity to train them anyway? And the plan to move on in 2-3 years is one which has been cultivated by the last few decades of employment norms so it's not fair to pin that one on the current group of juniors either, especially when it's equally likely most of your team will be around in 3 years either.
I do get smaller companies not being able to do it, but it seems like we're reaching a point where "smaller but growing" can be stretched to mean a company with a few hundred employees and if they don't have the ability to handle juniors it's hard to know what chance most people have of getting a start.
- magicalhippo 2y agoWe have capacity, but not a lot. Hence why we need to ensure it's not wasted. That said, sure, this isn't an issue with the latest crop. However I get the feeling from my more senior colleagues that this wasn't common back a couple of decades ago, at least here in Norway. But yeah, we've been 7 devs for a good while, we've grown to 12 over the last year or so, hence why a single person makes such a difference. Once we reach 20+ I fully expect to have room for more junior devs. If not we're doing it wrong.