,
3 tweets,
2 min read
Read on Twitter
Remember how the Software Industry mis-read one paper and got stuck with an "implementation described above [that] is risky and invites failure."
Yup, that was #Waterfall. We might have seen some sense with #agile and now we risk to undermine this again with #scaling nonsense
Yup, that was #Waterfall. We might have seen some sense with #agile and now we risk to undermine this again with #scaling nonsense
Turns out plenty has already been written on the pitfalls of scaling (yup, already in the 70's, 80's, 90's....) and there are some great books and papers that lay it out explicitly and bluntly. Some of these papers supposedly know by the industry.
If there is one paper you should read, it is "How Do Committees Invent?" by @conways_law.
It's not just the origin of "Conways Law", it's also packed with compelling observations about scaling and legacy systems we're doomed to write.
Read it today.
melconway.com/Home/pdf/commi…
It's not just the origin of "Conways Law", it's also packed with compelling observations about scaling and legacy systems we're doomed to write.
Read it today.
melconway.com/Home/pdf/commi…
