My line of thought - which is perhaps partly and indirectly based on "Small is beautiful" [1] applied by others to software - is that if "large project" is what gets you into (various) troubles, then you should avoid doing this. And indeed, the idea of breaking large projects into small, human-size components is a common "good practices" recommendation.
OTOH I experience quite the opposite everyday in the software industry, so I understand one could reject that position as too idealistic.
carlmr|3 years ago
Yes, you can always avoid making mistakes, but you can't make others avoid the same mistakes. It just never scales.
The software industry on the other hand is scaling heavily. Which is why what worked in the 80s isn't good enough anymore.
astrobe_|3 years ago
OTOH I experience quite the opposite everyday in the software industry, so I understand one could reject that position as too idealistic.
[1] https://en.wikipedia.org/wiki/Small_Is_Beautiful