My first experience developing software was in a group setting. It became clear to me that the three of us working in the lab were able to get more done than any one of us would have been able to independently. I could chime in when something made sense to me and listen closely if another person had a unique insight into a problem. The romanticized notion of a lone wolf hacker had no place there. We were working together as a team.
“I don’t usually tell people I am a software developer. I don’t want them thinking I am that type of person.”
– Chris Roth (@chrisrxth)
Since then I have found working in the industry that you actually do come across the occasional BOFH. You walk into a new job or start freelancing on a project and find someone who doesn’t “play well with others”. Maybe they didn’t participate in any sort of team activity growing up. It doesn’t have to be a sport. Social groups such as bands, clubs, and volunteer organizations are a great introduction to the world of software engineering. Teams need leadership, communication, and vested interests in addition to highly skilled people.
“The main ingredient of stardom is the rest of the team.”
– John Wooden