3 ms·
Build? Sure. Build well? These things aren't built perfectly the first time, or anywhere close. You don't always know what you're building until you've iterate
by darkerside 6y ago
Build? Sure.
Build well? These things aren't built perfectly the first time, or anywhere close. You don't always know what you're building until you've iterated on it a few times. It's just ready to forget that you didn't know when you have the benefit of hindsight.
And build well and maintain? Not a chance. This should be obvious.
Maybe we have different ideas off what a small team is. To be, 3-4 devs is a small team. In context, I could say maybe ten developers, but I would consider that a large team. At that point I'd be preparing to split into multiple teams.
In not saying they needed 21,000, but it's likely we just mean completely different things when we talk about a small team. What does it mean to you?
- onion2k 6y agoI guess you missed the word "iterate" in my post. Good software doesn't spring in to existence just because a team has talent. It starts off OK if you're lucky and it evolves in to something good if the team can guide it properly.
- darkerside 6y agoI'll ask again, when you say a small team, what exactly are you thinking about? Order of magnitude is fine. 3? 30? 300?