Advertisement
Advertisement

More Related Content

Advertisement

Building Software That Lasts - Voxxed Days Singapore

  1. Building Applications That Last Voxxed Days Singapore 2018 Kris Howard aka @web_goddess
  2. ⚠ "
  3. December 1996
  4. December 1996
  5. 6 months
  6. 2 years
  7. 3 years
  8. 3 years
  9. 3 years
  10. 3 years
  11. 4 years
  12. 4.5 years
  13. 5 years
  14. 5 years
  15. 5 years
  16. Fast forward 14 years…
  17. 19 years
  18. So what to do?
  19. LEGACY CODEBASE #
  20. Legacy Software $ Rewrite it completely $ OR ⛵ Incremental redevelopment ⛵
  21. Why to Rewrite • The code is a mess. • The application is slow. • The code is ugly. • We’ll get it right this time! • We picked the wrong platform.
  22. Characteristics • Ability to evolve over time • Separation of concerns • Use of standard languages • Minimising of dependencies • Simple, readable code • Fault-tolerance and fast recovery
  23. Back to my story…
  24. Wordpress?
  25. Best practices • Coding standards and code reviews • Static analysis tools • Defensive programming
  26. Best practices • Coding standards and code reviews • Static analysis tools • Defensive programming • Property-based testing
  27. Best practices • Coding standards and code reviews • Static analysis tools • Defensive programming • Property-based testing • The Campsite Rule • Documentation
  28. Thanks! @RoaldDahlFans roalddahlfans.com Kris Howard @web_goddess web-goddess.org
Advertisement