$30 off During Our Annual Pro Sale. View Details »

How not to have future developers curse you

Keith Pitty
November 13, 2018
Technology
1
60

How not to have future developers curse you

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

Keith Pitty

November 13, 2018
Tweet

More Decks by Keith Pitty

See All by Keith Pitty
Succeeding with Remote Retrospectives
keithpitty
0
70
What were they thinking?
keithpitty
0
150
How not to give advice (about Markdown)
keithpitty
0
74
Why I use Guard
keithpitty
0
130
Morphing your Ruby into Civil Tech
keithpitty
0
60
Loving Legacy Code
keithpitty
0
420
Better OO Design in Rails
keithpitty
0
50

Other Decks in Technology

See All in Technology
Code Graphology
fr0gger
0
140
金融システムにおけるクラウドネイティブなアーキテクチャ設計とその構築
tetsun
0
170
Oracle Autonomous Database：サービス概要のご紹介
oracle4engineer
PRO
0
510
re:Growth2022「Analytics系アップデートまとめ」
sutotakeshi
0
180
JAWS-UG 朝会 #40 登壇資料
takakuni
0
270
ML開発におけるML PMの関わり方事例
line_developers
PRO
1
620
What's Data Lake ? Azure Data Lake best practice
ryomaru0825
3
1.3k
Accelerated Computing on AWS for NLP
icoxfog417
1
290
EMになって半年でやったこと
yuu26
0
330
オラクルのブロックチェーンソリューションご紹介 /blockchain
oracle4engineer
PRO
0
1k
PWA開発を基礎からおさらい / PWA Night CONFERENCE 2022
chinen
2
560
ECS の IPv6 がムズカシイ
eterny13
0
150

Featured

See All Featured
Three Pipe Problems
jasonvnalue
89
8.9k
Streamline your AJAX requests with AmplifyJS and jQuery
dougneiner
127
8.7k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
13
1.1k
Debugging Ruby Performance
tmm1
67
11k
How to Ace a Technical Interview
jacobian
269
21k
The Art of Programming - Codeland 2020
erikaheidi
35
11k
Designing the Hi-DPI Web
ddemaree
273
32k
What's in a price? How to price your products and services
michaelherold
231
9.6k
Code Review Best Practice
trishagee
48
11k
Code Reviewing Like a Champion
maltzj
508
38k
Keith and Marios Guide to Fast Websites
keithpitt
405
21k
The Web Native Designer (August 2011)
paulrobertlloyd
76
2.1k

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?