3 ms·
>It took 60 people 3 years to not produce a correctly working service. [...] She spent 3 months building it. Using 60 people to produce something 1 person coul
by jffhn 4y ago
>It took 60 people 3 years to not produce a correctly working service. [...] She spent 3 months building it.
Using 60 people to produce something 1 person could do, is like cutting this person's brain in 60 parts and connecting them with 1Hz data links.
V. Lextrait (CTO of Amadeus at the time if I recall properly) had a rule of only splitting a piece of work between multiple developpers if it couldn't fit in the otherwise single developper's head.
- quickthrower2 4y agoIt is worse than that. Try to get 60 people to pick up one spoon for example. The coordination overhead and arguing “which spoon” and “we should consider picking up a knife!” means it is easier for one person. Otoh, searching for a criminal in the woods is embarrassingly parallelizable and would benefit from a 60 search party (forget dogs in this imperfect analogy). Most software dev like the spoon is not super parallelizable. But probably more amenable to a single person working on each project than developers think.