10 software essays that changed how I think

This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).

A curated collection of 10 influential software engineering essays spanning 1989-2022, covering technology selection (Choose Boring Technology), type safety (Parse Don't Validate), refactoring strategy (never rewrite from scratch), monolith vs microservices architecture, team process health (Joel Test), API design principles, simplicity over perfection (Worse is Better), complexity management, quality-speed tradeoffs, and career positioning. Each essay is accompanied by personal lessons learned and practical applications, emphasizing pragmatism, simplicity, and business value over technical perfectionism.

โ€ข25m read timeโ€ขFrom newsletter.techworld-with-milan.com
Post cover image
Table of contents
GitHub Actions analytics - whatโ€™s actually happening (Sponsored)1. Choose Boring Technology (2015) by Dan McKinley ๐Ÿ”—2. Parse, Donโ€™t Validate (2019) by Alexis King ๐Ÿ”—3. Things You Should Never Do, Part I (2000) by Joel Spolsky ๐Ÿ”—4. The Majestic Monolith (2016) by David Heinemeier Hansson (DHH) ๐Ÿ”—5. The Joel Test (2000) by Joel Spolsky ๐Ÿ”—6. How to Design a Good API and Why It Matters (2007) by Joshua Bloch ๐Ÿ”—7. The Rise of โ€œWorse is Betterโ€ (1989) by Richard P. Gabriel ๐Ÿ”—8. The Grug Brained Developer (2022) by Carson Gross ๐Ÿ”—9. Software Quality at Top Speed (1996) by Steve McConnell ๐Ÿ”—10. Donโ€™t Call Yourself a Programmer (2011) by Patrick McKenzie ๐Ÿ”—11. Bonus: How To Become a Better Programmer by Not Programming (2007) by Jeff Atwood ๐Ÿ”—12. Conclusion๐Ÿ“ฐ What I read daily (you can subscribe to it too!)More ways I can help youWant to advertise in Tech World With Milan? ๐Ÿ“ฐLove Tech World With Milan Newsletter? Tell your friends and get rewards.
4 Comments

Sort: