10

Another rant reminded me:

I’ve been at the same company for almost five years now, and I’ve seen the dev teams grow: several juniors come in, and even a few that left - or more precisely, was let go. And for each of those that were let go, the root issue with them was always the same: not the lack of skills or ability to learn their trade at job, no. It was always communication issues serious enough to render working with them impossible.

So remember juniors, besides googling and problem solving, the most important skill to master in team-based dev envs is COMMUNICATION. You need to fucking be part of the team or you’re out, no matter how good you are technically. If that’s too hard, either this is the wrong line of work for you or you need to just go solo. It’s that simple, boys, girls, and everyone else on the spectrum.

Comments
  • 3
    Very true, having been in the business a few decades more I have seen the same thing, unless your really a stellar dev that are good enough for every one else to accept the diva behavior any line wolf will only harm the team by causing integration problems or merge conflicts that waste whatever value they add to the team.
  • 0
    Many people end up learning programming because they don't want their main task to be communicating with people. Yet that's what they may end up working on most of the time. Maybe part of the problem is that teams are unable to create a working culture that works well for the team. Not every team should operate by the same terms.
  • 1
    @electrineer fair point, to a degree. Nonetheless, I cannot imagine teamwork without communication.
  • 1
    @100110111 it kind of is in the name ;), without communication you do not have a team.

    Sure, not everyone on the team should need to talk to everyone, some will work better if they only have to talk to the rest of the team and that is usually fine, its usually helpful to have one path of communication in and out of the team so tasks do not get lost.
Add Comment