@ashfurrow The problem is a kid's learned one hammer so that's all they apply to every problem. And the industry hires young inexperienced kids because they're cheap. And then none of our software works worth a shit.
Consultants are worse, because they should know better, but don't bother.
@mdhughes it makes me feel weird to see you call junior developers “kids” – and in any case, it was just a meme. I haven’t even written Java in nine years.
@ashfurrow I do call everyone under 30 "kids". It's very hard to distinguish them from this far side of the event horizon.
I mostly quit Java in 2008, but still maintain a few tools and it keeps those circuits active in my memory.
@mdhughes Aren't your interactions with junior developers then constrained by looking at them as children?
I learn a lot from the juniors I work with, and even in areas where I _am_ an expert, I consider newcomers to be peers.
@ashfurrow If they've specialized in something new, they might have had time to develop one useful skill, but generally the "kids" are literally where I was 2-3 decades ago.
I'm OK with teaching them, as long as I have time, but wouldn't trust their checkins without review.
I also don't have to collaborate a lot, just solve customer problems (often created and left behind by juniors) or work on my own things. If I had to be in a giant corporate machine again that'd be a different social problem.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!