100% agree, except I'd add that the lone wolf doesn't really work to well even in a larger company. Even in a larger company, I still try to break down teams to be a max of no more than 10 people total... including QA/SDETs. So, you'd still get the small team dynamic. But, I was trying to be benign earlier because for me, CP is just a place to argue with people who have no experience in the subject they are arguing about. And well, that gets old. But totally agree with this.
Sander Rossel wrote:We can't afford a lone wolf right now.
Sander Rossel wrote:Programming complex systems with more than one person should always be a team effort, not a two-(or-more)-people-apart effort.
Preaching to the choir, buddy.
That's a sign of good leadership. Creative people are rebellious by nature (we can make something better, new, etc.) but in my experience, if you let a dev know the why something is they'll usually accept it rather than just say "because I said so." Well, assuming they're good devs and assuming the why isn't totally off the wall.
Sander Rossel wrote:why they're important.
Sander Rossel wrote:I'm an employer, but also still very much a programmer
Don't ever lose that man. Steve Jobs (or anyone who's intelligent) believed the best managers (which an employer is to start with) started off as a dev. Not one of the clowns who's in it for the money or to just tell other people what to do. Programmers inherently have more respect for someone being one of their own. They may not always say it for fear of getting fired, etc. But, it's true.