The document discusses various ways to avoid accumulating technical debt when managing infrastructure and security as an operations team. It recommends automating processes like deployments, upgrades, and monitoring to reduce manual work. Other tips include using tools that isolate services, following security advisories, and documenting procedures to avoid "derployments" during incident response. The overarching message is to embrace automation to save time and minimize human errors that can introduce technical debt.

1. Avoiding Toxic
Tech Debt
Sad Stories By
R Tyler Croy

3. Welcome to the future

4. Welcome to the future

5. You're an ops now

6. You will need
independent
infrastructure

7. Choosing tools

8. Choosing tools

9. Tech debt

10. Tech debt

11. Tech debt

12. Automation

13. Automation

14. Automation

15. Security

16. Managing secrets

17. Managing secrets
- Certificates
- Signing keys
- API keys / tokens

18. Managing secrets
- Certificates
- Signing keys
- API keys / tokens

19. Access control

20. Access Control
- GitHub Organization
- LDAP
- Artifactory
- Jenkins Matrix Authorization
- SSH keys

21. Access Control
- *GitHub Organization*
- LDAP
- Artifactory
- Jenkins Matrix Authorization
- SSH keys

22. Access Control
- GitHub Organization
- *LDAP*
- Artifactory
- Jenkins Matrix Authorization
- SSH keys

23. Access Control
- GitHub Organization
- LDAP
- *Artifactory*
- Jenkins Matrix Authorization
- SSH keys

24. Access Control
- GitHub Organization
- LDAP
- Artifactory
- *Jenkins Matrix Authorization*
- SSH keys

25. Access Control
- GitHub Organization
- LDAP
- Artifactory
- Jenkins Matrix Authorization
- *SSH keys*

26. Service balkanization

27. Service balkanization
- Virtual machines
- Jails/chroot
- Containers

28. Service balkanization
- *Virtual machines*
- Jails/chroot
- Containers

29. Service balkanization
- Virtual machines
- *Jails/chroot*
- Containers

30. Service balkanization
- Virtual machines
- Jails/chroot
- *Containers*

31. Security Lifecycle

32. Security Lifecycle
- Security advisory lists
- Automation => Easier upgrades
- Don't be dumb

33. Security Lifecycle
- *Security advisory lists*
- Automation => Easier upgrades
- Don't be dumb

34. Security Lifecycle
- Security advisory lists
- *Automation => Easier upgrades*
- Don't be dumb

35. Security Lifecycle
- Security advisory lists
- Automation => Easier upgrades
- *Don't be dumb*

36. Security

37. Security

39. Manual work

40. "Automating
this
is hard"

41. "Automating this is hard"
- Difficult services
- Custom packaging
- Monitoring

42. "Automating this is hard"
- *Difficult services*
- Custom packaging
- Monitoring

43. "Automating this is hard"
- Difficult services
- *Custom packaging*
- Monitoring

44. "Automating this is hard"
- Difficult services
- Custom packaging
- *Monitoring*

45. Incident response

46. Incident response
- Application problems
- Resource exhaustion
- Cache issues
- Insufficient file descriptors
- Log rotation

47. Incident response
- *Application problems*
- Resource exhaustion
- Cache issues
- Insufficient file descriptors
- Log rotation

48. Incident response
- Application problems
- *Resource exhaustion*
- Cache issues
- Insufficient file descriptors
- Log rotation

49. Incident response
- Application problems
- Resource exhaustion
- *Cache issues*
- Insufficient file descriptors
- Log rotation

50. Incident response
- Application problems
- Resource exhaustion
- Cache issues
- *Insufficient file descriptors*
- Log rotation

51. Incident response
- Application problems
- Resource exhaustion
- Cache issues
- Insufficient file descriptors
- *Log rotation*

52. Laziness

53. Laziness

54. Manual work

55. Manual work

57. Derployment

58. Derployment
- Document deployment processes
- Continuous delivery saves time

59. Derployment
- *Document deployment processes*
- Continuous delivery saves time

60. Derployment
- Document deployment processes
- *Continuous delivery saves time*

61. Derployment

62. Good luck

63. Good luck

64. Go automate