|
|
|
|
|
|
by thirtyfivecent
1467 days ago
|
|
|
This is only true if you're a beta bucks provider doing CRUD to support a family. There are plenty of real programmers out there working on their own projects and the hard part in these WORTHWHILE projects is certainly the programming :) |
|
|
Leading a team or joining a new one? It's translating what the company needs into the set of instructions. Ambiguity in that process leads to stalled juniors, even if they're excellent coders. I've been there, both as the frustrated demoralized junior and, later in my career, as the team lead trying to make that process work.
Yes, I'd be concerned if someone literally cannot write compilable code in the programming language you're working in. But usually if someone makes it far enough to be employed there's something else going on if they're producing serious garbage. Skill, attitude, motivation, team morale, or bad instructions and bad leadership. Honestly, my experience in seeing teams dysfunction is that it's best to start from the end of that list and move backwards.