Today we have part 3 in our 3 part series on the Titanic Effect ( https://www.titaniceffect.com/competitors), a book by Todd Saxton, Kim Saxton, Michael Cloran. In this episode, we talk with Michael Cloran, who created the technical ocean of the Titanic Effect. This ocean covers a lot of concepts that in general describes the process of building up technical debt as you begin a technical project, such as a code base that is difficult to edit and modify, architectural decisions that were made early on, or it could be processes where your developers aren’t following up on best practices. He also shares some of the technical debt that he can now recognize he created in some of his earlier projects.
“When it comes to technology, as a founder, stop thinking that you can abdicate. You’re going to have to read and understand a little bit about design, and this is a great place to start.
— Michael Cloran
Topics in the episode
The three seas of the technical ocean: validation, design, and development
Biggest sources of technical debt within each ocean
The importance of running a quick test to validate a concept
False hope drift of icebergs
Value of building a vision in the early stages
Exercises in building a vision