I've worked with similar people but I think everyone has a place their suited to work in. That kind of person can be a great hire in a very small team where they are running the codebase, just you wouldn't want them at your fortune 500 trying to get them to care about Agile
-
-
Replying to @AlexRoseGames @mode7games
I've worked in some small teams and I've never been in a team small enough that their problems weren't problems. Maybe if you have literally 3-4 people. But as soon as you scale to the point they need to work with others on a live consumer product, it's more bad than good imo
2 replies 0 retweets 0 likes -
Replying to @tactful @mode7games
Yeah I'm talking about small small, like "1 programmer on backend, one on product, plus artists/product manager". i.e. startups. if your business is really small there's definitely a place for people who aren't great for team coding but do amazing solo work
1 reply 0 retweets 2 likes -
Replying to @AlexRoseGames @mode7games
Yeah, totally fair, those problems only become problems when such people brush against other people. Nobody to brush against if you have sole ownership of engineering lol
1 reply 0 retweets 1 like -
Replying to @tactful @mode7games
I think this becomes really clear in game jams. You see the big teams with 4 programmers and a designer and 2 artists normally don't even get far past the planning stage while one stupidly good all rounder just cleans up the whole jam on their own
1 reply 0 retweets 1 like -
Replying to @AlexRoseGames @mode7games
I went from a team of 30 to a team of 2 and the freedom was so liberating at first. If I had an idea, I could do it, there were no stakeholders, I didn't need sign off or consensus. Felt like I was moving so fast. After 6 months I got sick of it + struggled to do bigger projects
0 replies 0 retweets 0 likes -
Replying to @tactful
I think the main problem with big teams is you simply can't find 30 geniuses. The more people you hire, the more you have to assume everyone is the slap bang average worker and the only way you can get output from them is a system like agile that slowly squeeses out productivity
1 reply 0 retweets 0 likes -
Replying to @AlexRoseGames @tactful
and likewise the more you scale in programming, the less people know about the overall codebase and only know their own domain, the less "vision". But for a large company with many clients you simply need that, 4 people isn't enough
1 reply 0 retweets 0 likes
Yeah I dunno, I feel like I have to believe it's possible to scale without compromising quality of the people you hire. Otherwise it makes me sad. And even if you bring on board THE BEST people, it's still hard to be aware of what's going on when you have 10-20-30 great people
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
