National Coding Day 2026 - Software Evolution: The Complete Lifecycle

Transcript

1. Software Evolution - The Complete Lifecycle National Coding Day 2026-01-24
2. Karn Wong Loves optimization Has too much fun cranking out benchmarks HashiCorp Ambassador & AWS Community Builder Website: karnwong.me Independent Consultant
3. It starts with a POC
4. What a POC Should Be MVP Not over-engineered Has some tech debts
5. The fun starts when it’s time to productionize 💣
6. This Should Happen in Production Tech debts, begone Take your time, but not too long Fix it now or later, your call
7. Software is evolving
8. Let there be changes
9. Then things got slow 🥹
10. Refactor?
11. What if I don’t want to refactor?
12. Yak Shaving 🦬 Also known as ถางหญ้า 🌿
13. These Will Happen 🐌 Devs will get frustrated Organizational knowledge loss Revenue loss 💸
14. And things will slow down
15. Sometimes it’s time to let go All things must come to an end
16. Appendices What can go wrong?
17. Storage Backend Disk? Blob storage? (S3, GCS, Blob, etc.)
18. Database Engine OLTP - Online Transaction Processing OLAP - Online Analytical Processing Key-Value Document Schema migration?
19. Networking Workloads can’t communicate across VPCs You can’t change CIDR in-place VPC Peering VPC B 100.200.1.1 100.200.1.2 VPC A 100.200.1.1 100.200.1.2 CIDR clash 💥
20. Portability Vendor agnostic? Containerize-able? Think early
21. Takeaways Validate ideas first Early-stage tech debts are fine Tech debts can slow things down Refactoring has a price It’s okay to end a project Some mistakes are very hard to rectify
22. Thank you 🙏 Download slides at: karnwong.me