How not to have future developers curse you

A871f5bf1b1a48262a04ec49bc60fa77?s=47 Keith Pitty
November 13, 2018

How not to have future developers curse you

Lightning talk given at rorosyd (Ruby or Rails Oceania Sydney) meetup on 13th November, 2018.

A871f5bf1b1a48262a04ec49bc60fa77?s=128

Keith Pitty

November 13, 2018
Tweet

Transcript

  1. How not to have future developers curse you @keithpitty

  2. Code

  3. What?

  4. Reflect…

  5. What can you do?

  6. New code

  7. Design principles?

  8. OO?

  9. Functional?

  10. Combination?

  11. Separation of concerns

  12. Easy to read

  13. 4 rules of simple design

  14. 1. Tests pass

  15. 2. Expresses intent

  16. 3. DRY

  17. 4. Small

  18. Automated tests

  19. Continuous Integration

  20. Continuous Deployment

  21. Maintenance

  22. Planned

  23. Upgrades!

  24. Legacy code

  25. Aim to rescue

  26. Automated tests

  27. Refactor

  28. Upgrades!

  29. Decommision?

  30. Represent developers

  31. Persuade decision-makers

  32. Educate non-developers

  33. Aim high!

  34. Up to the challenge?