Infrastructure Debt

Talk I gave at Lone Star PHP 2012 about infrastructure debt and friction, basically the "bills" you have to pay to get code from development to shipped

Transcript

1. Infrastructure debt Chris Hartjes Lone Star PHP -- June 30, 2012 @grmpyprogrammer
4. What is Infrastructure Debit?
6. It is the price of getting code from idea to Shipped
7. Reg Braithwaite (@raganwald) “Debt and friction both accumulate, but debt must be "repaid" in a lump sum. If "technical debt" or "infrastructure debt" means your velocity is falling over time, it's friction, not debt.”
8. Think of things in terms of bills to be paid
9. BILL #1 Version control
10. There is no excuse to not use version control
12. File sharing is not version control
13. No version control means you cannot easily share and UPDATE files
14. Bill #2 Consistency in environments
15. “Works for me...”
16. Vagrant
17. “Create and configure lightweight, reproducible, and portable development environments.” http://vagrantup.com
19. Everything needs to be the same everywhere
20. Too many moving parts?
21. Bill #3 Non-automated Depoyment
23. “If you find yourself doing something twice, make the computer do it!”
24. Capistrano Not the place the swallows go to
25. PHing Is Not GNU make
26. People Make Mistakes
27. BILL #4 Logging
28. E_STRICT RIGHT?!?!?!
29. Everyone should see the logs who can help fix things
30. Centralized logs hide no secrets
31. Do your own logging
32. BILL #5 No Coding Standard
33. “All the code in the same language in your application should look the same”
34. PHP_CodeSniffer
35. “Context shifts to understand code that always looks different has a real cost”
36. BILL #6 Siloing Developers
37. “You have a team, make them act like a team”
40. “Cross-functional teams get more done”
42. Debt Needs To Get Paid
43. Don’t Accept Things As The Way It Always Will Be
44. Thank you!
45. http://www.littlehart.net/atthekeyboard @grmpyprogrammer http://joind.in/6356