Repeat yourself, do more than one thing, and... — programming is terrible
If you ask a programmer for advice—a terrible idea—they might tell you something like the following: Don’t repeat yourself. Programs should do one thing and one thing well. Never rewrite your code...
If you ask a programmer for advice-a terrible idea-they might tell you something like the following: Don't repeat yourself. Programs should do one thing and one thing well. Never rewrite your code from scratch, ever!. Following "Don't Repeat Yourself" might lead you to a function with four boolean flags, and a matrix of behaviours to carefully navigate when changing the code. Splitting things up into simple units can lead to awkward composition and struggling to coordinate cross cutting changes. Avoiding rewrites means they're often left so late that they have no chance of succeeding. The advi
Explore this link on the map →saved by
related reading
- Cognitive load is what mattersminds.md
- The Grug Brained Developergrugbrain.dev
- Things You Should Never Do, Part I – Joel on Softwarejoelonsoftware.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- AHA Programming 💡kentcdodds.com
- notes/books/pragmatic-programmer.md at master · pkardas/notes · GitHubgithub.com
- Reflections on 10,000 Hours of Programming | Matt Rickardmatt-rickard.com
- Frontend Developer: Do Repeat Yourself | Szymon Chudychudy.me
- Goodbye, Clean Code — overreactedoverreacted.io
- Michael Feathers - 10 Papers Every Developer Should Readmichaelfeathers.silvrback.com
- On bad advicescattered-thoughts.net