Download as KEY, PPTX
Uploaded byMartijn Verburg
Modern software development anti patterns (OSCON 2012)
The document discusses 10 modern software development anti-patterns: conference-driven delivery, mortgage-driven development, being distracted by shiny new technologies, design-driven design, using all design patterns like Pokémon, tuning by folklore instead of measuring performance, putting all code in one file, treating software development like a lean startup, and making things up without a plan. The author argues against these approaches by suggesting to prototype instead of rushing, design for current rather than future needs, use appropriate design patterns, measure performance empirically, separate components, and take a business-focused approach to continuous delivery.
More Related Content
Similar to Modern software development anti patterns (OSCON 2012)
![[BDD 2025 - Artificial Intelligence] AI for the Underdogs: Innovation for Sma...](https://cdn.slidesharecdn.com/ss_thumbnails/ai-aifortheunderdogsinnovationforsmallbusinesses-251124030839-72a599a4-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] Digital Accessibility: Why Developers nee...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-digitalaccessibilitywhydevelopersneedtoknowandcarein2025-251127011019-0674441d-thumbnail.jpg?width=640&height=640&fit=bounds)
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
![[BDD 2025 - Full-Stack Development] The Modern Stack: Building Web & AI Appli...](https://cdn.slidesharecdn.com/ss_thumbnails/fs-themodernstackbuildingwebaiapplicationswithserverless-251124030844-388cf04f-thumbnail.jpg?width=640&height=640&fit=bounds)
Modern software development anti patterns (OSCON 2012)
- 2. And “The Voice ofReason”
- 3. PRESENT Modern Software Development Anti-Patterns Reconciliation by Scot A Harvest
- 4. 1. Conference-Driven Delivery
- 5. Hecklers that suggestthis talk resembles this anti-pattern...
- 7. Real pros hackcode and write their slides minutes before their talks 7
- 8. The Voice ofReason PPPPPP
- 9. 2. Mortgage-Driven Development
- 10. In these tough economictimes.. 10
- 11. The Voice ofReason Don't succumb to fear
- 12. 3. Distracted ByShiny
- 13.
- 14. Always use thelatest tech, it'll put you ahead 14
- 15. The Voice ofReason Prototype and evaluate
- 16. 4. Design DrivenDesign
- 17. UML Code Generators are awesome 17
- 18. The Voice ofReason Design for what you need now
- 19.
- 20. Use *all* ofthe GoF design patterns 20
- 21. The Voice ofReason The appropriate design pattern is your friend
- 22. 7. Tuning byFolklore
- 23. I performance tuneby lighting black candles 23
- 24. The Voice ofReason Measure, don't guess.
- 25.
- 26. All the codein one file.. easier to search 26
- 27. The Voice ofReason Discrete components are vital in today's distributed world
- 28. 9. Lean StartupNinja
- 29. Compiles? == Shipit! 29
- 30. The Voice ofReason Continuous Delivery is a business enabler
- 31.
- 32. I'll make itup as I go along 32
- 33. The Voice ofReason I'll prove Martijn wrong :-)
- 34. Thanks! Martijn -@karianna & Ben - @kittylyst
Editor's Notes
- #2 \n
- #3 We have all of these tools and techniques, but are we any better?\n
- #4 Note the lack of fluffy animals in this talk - that's right people this shit just got serious\n
- #5 \n\n
- #6 Nothing to do with this talk whatsoever!\n\n
- #7 \n
- #8 \n
- #9 Proper preparation prevents piss poor performance\n
- #10 \n
- #11 source code on a USB key, no documentation, don't communicate etc\n
- #12 Don't be a Cave Troll\nDocumentation\nCoding is a social activity\n
- #13 Always use the latest bleeding edge technologies!\nNo IDE support? Well you an just use vi like a real developer right?\nYou'll be on hacker news!\n
- #14 \n\n
- #15 No IDE support? Well you an just use vi like a real developer right?\nYou'll be on hacker news!\n
- #16 Carfey.com search for why developers keep make technology choices\nboredom, CV++, Peer Pressure, Lack of understanding, solving non-existing problems\n
- #17 UML is king\nGenerate your code from UML\n
- #18 \n
- #19 \n
- #20 Gotta catch them all!\nMust use at least 5 of the GoF\n
- #21 Gotta catch them all!\nDefaultAbstractFactoryFactoryBean\n
- #22 Lifecycle: Design Pattern --> Framework --> Language Feature\n
- #23 \n
- #24 \n
- #25 Empirical evidence trumps intuition\n
- #26 \n
- #27 \n
- #28 Empirical evidence trumps intuition\n
- #29 \n
- #30 \n
- #31 Empirical evidence trumps intuition\n
- #32 \n
- #33 \n
- #34 Empirical evidence trumps intuition\n
- #35 \n