"High Optionality Programming" - the practice of paying a small design & programming premium today in order to avoid a massive accumulation of technical debt later. This is a technique we've succesfully used at large scale in our previous business and in the businesses of many of our customers. The key to implementing high optionality programming correctly is to assess the likelihood of a future change to your system and to plan for its eventuality in advance when it's cheap to do so: early on in the software development lifecycle.
In this video we explain the concepts behind high optionality programming, offer some case studies of how it's been used successfully, and introduce the techniques we're going to cover in the second video that demonstrate how to actively curb the long-term accumulation of technical debt in software projects.
See Part 2 here: https://www.youtube.com/watch?v=sD6W4n-Ksfs
Links:
Hire Petabridge: https://mailchi.mp/petabridge.com/4izk50pskb
Blog Post: https://petabridge.com/blog/high-optionality-programming-pt1/
CodeOpinion "Does a Data Access Layer make it easier to change your Database?" https://www.youtube.com/watch?v=_IXEfi1B-lA
Technical Debt Cartoon: https://vincentdnl.com/drawings/
Introduction (0:00)
Technical Debt (0:40)
Optionality in Software (4:50)
Case Study (10:26)
High Optionality Techniques (20:26)
