✳flâneur — a map of the web's best reading
The Programmer's Paradox: Systems Thinking
theprogrammersparadox.blogspot.com · 3,119 words · saved by 1 readers
A blog about software development and programming.
The Programmer's Paradox: Systems Thinking Thursday, February 5, 2026 Systems Thinking There are two main schools of thought in software development about how to build really big, complicated stuff. The most prevalent one, these days, is that you gradually evolve the complexity over time. You start small and keep adding to it. The other school is that you lay out a huge specification that would fully work through all of the complexity in advance, then build it. In a sense, it is the difference between the way an entrepreneur might approach doing a startup versus how we build modern skyscrapers
Explore this link on the map →saved by
related reading
- The Programmer's Paradox: Fragmentationtheprogrammersparadox.blogspot.com
- The Grug Brained Developergrugbrain.dev
- Things I believe · GitHubgist.github.com
- On architecture, urban planning and software construction - Tomas Petricektomasp.net
- notes/books/pragmatic-programmer.md at master · pkardas/notes · GitHubgithub.com
- The Programmer's Paradox: Waterloo Styletheprogrammersparadox.blogspot.com
- Systems design explains the world: volume 1 - apenwarrapenwarr.ca
- Computers can be understood - Made of Bugsblog.nelhage.com
- Big Ball of Mudlaputan.org
- 202012 - apenwarrapenwarr.ca
- 20 Things I've Learned in my 20 Years as a Software Engineer - Simple Threadsimplethread.com
- Software engineering is about thinking, not typing | Organizing Chaosjordankaye.dev