The user narrator (also last page) also raises an interesting point:
>> I'm surprised this article didn't mention test driven development for building large pieces of software!
^ He then makes a good case for TDD.
TBH I don't see much improvement in quality at all reading the top comments. Some are dead wrong, for example, the user snidane says (which is/was in the top three on the first page if you ignore nested sub-comments):
>> The tooling is simply not there, so every software project keeps pushing the boundary of what is possible in its own unique fragile way.
Not only is that comment dead wrong (the tooling is definitely there, I've worked on some of these scalability open source tools), it contradicts another comment just above it (by user the_duke) which received just a few more votes:
>> At scale software stops being a technology problem and becomes a people problem. And groups of humans don't scale.
Also, user ailmanki (also last page) said:
>> Every system requires sooner or later another system on top. https://en.m.wikipedia.org/wiki/Chaos_theory
That would explain what is happening.
The user narrator (also last page) also raises an interesting point:
>> I'm surprised this article didn't mention test driven development for building large pieces of software!
^ He then makes a good case for TDD.
TBH I don't see much improvement in quality at all reading the top comments. Some are dead wrong, for example, the user snidane says (which is/was in the top three on the first page if you ignore nested sub-comments):
>> The tooling is simply not there, so every software project keeps pushing the boundary of what is possible in its own unique fragile way.
Not only is that comment dead wrong (the tooling is definitely there, I've worked on some of these scalability open source tools), it contradicts another comment just above it (by user the_duke) which received just a few more votes:
>> At scale software stops being a technology problem and becomes a people problem. And groups of humans don't scale.