Re:Worker-owned tech cooperatives find a niche near Silicon ...
by anonhn82 on Thursday May 28, 2015 @08:27PM
(#9622034)
If this is such a good way to run a tech company, why isn't it also a good way to develop software? In other words, why are projects led by BDFLs like Linux and Python so successful, while the design-by-committee approach is usually regarded as producing substandard outcomes?
[ Parent
| on HN ]
Re:Worker-owned tech cooperatives find a niche near Silicon ...
by nickpsecurity on Friday May 29, 2015 @12:42AM
(#9622710)
Depends on the committee. The Ada designers, acting on committee's needs, came up with pretty much what they wanted. Had performance, availability and pricing issues that kept it from taking off as much as it could. Yet, the language's features accomplished their goals very well as proven by a number of empirical studies by military and defense contractors.
So, that's one success story. Anyone have any other examples? I'm asking because I really think this recurring theme is a myth about committee-design languages where the problem really is a prevalence of bad committees.
Re:Worker-owned tech cooperatives find a niche near Silicon ...
by thaumaturgy on Thursday May 28, 2015 @09:08PM
(#9622159)
Because the software development industry is stupidly fragmented.
Get 12 developers together in a room and you'll get 12 different answers on the best way to build anything.
Re:Worker-owned tech cooperatives find a niche near Silicon ...
by michaelchisari on Friday May 29, 2015 @02:11AM
(#9622991)
It's a cultural problem, definitely.