2 ms·
To extend on that: there needs to be a small set of cooks with their actual fingers in the broth (for various reasons including coordination and quick pivots) b
by kqr 4y ago
To extend on that: there needs to be a small set of cooks with their actual fingers in the broth (for various reasons including coordination and quick pivots) but that small group should probably consult a much larger group of kitchen staff and customers (read: potential users, collaborators, partners, etc) to figure out if they're going the right direction.
- yashap 4y agoOh yeah, it’s definitely not about making decisions in isolation - do your research, talk to stakeholders, think them through! Anyone who is given decision making power, and uses that to just do whatever they like with minimal consideration/research/etc., needs to have that power removed. But I do think in the early stages of a project, the number of people ultimately making the decisions (and writing code) needs to be small. More people can be added later, if necessary, but in the early stages of a greenfield project the team must be small. I’ve been on projects where 10-20 people are thrown onto it before a line of code exists and it’s an absolute shit show: decisions take ages, devs are constantly stepping on each other’s toes and extremely unproductive, there’s no personal accountability, etc.