The Programmer's Paradox: Fragmentation
theprogrammersparadox.blogspot.com · 1,651 words · saved by 1 readers
Software is a static list of instructions, which we are constantly changing. Thanks for the Feedback!
The Programmer's Paradox: Fragmentation Thursday, December 14, 2023 Fragmentation When you have never experienced large-scale software development, your preference is often to prefer fragmentation. You want lots of little parts. It’s understandable. Most people are taught to decompose large problems into smaller ones. Once they have completed that, they assume that all of those smaller sub-solutions are mostly independent from each other. They believe that dealing with each piece independently would be easier. That way you can just focus on one and ignore the rest. It’s just that w
related reading
- The Programmer's Paradox: Systems Thinkingtheprogrammersparadox.blogspot.com
- The Programmer's Paradox: Waterloo Styletheprogrammersparadox.blogspot.com
- The Grug Brained Developergrugbrain.dev
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Cognitive load is what mattersminds.md
- Computers can be understood - Made of Bugsblog.nelhage.com
- Repeat yourself, do more than one thing, and... — programming is terribleprogrammingisterrible.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- How to write complex softwaregrantslatton.com
- notes/books/pragmatic-programmer.md at master · pkardas/notes · GitHubgithub.com
- Advice for new software devs who've read all those other advice essays • Buttondownbuttondown.email
- How To Do Lessalexturek.com