Summary of OutSystems | OSDC Talks - The True cost of Technical Debt - Truewind

00:00:00 - 00:30:00

OutSystems discusses the conflict between developers and managers when it comes to developing software, and how technical debt can lead to a lack of development speed. The video discusses the importance of having a good understanding of the feature being implemented in order to design the right architecture, and how a lack of understanding by either group can lead to problems down the road.

• 00:00:00 Technical debt is a term coined by Ward Cunningham. It refers to code that is compromised in order to speed up development. There is a conflict between the need for speed and the need for quality, and it is important to be aware of this when building up technical debt.
• 00:05:00 The video discusses the conflict between developers and managers when it comes to developing software, and how technical debt can lead to a lack of development speed. OutSystems discusses how technical depth can lead to this conflict, and how reducing that depth can help improve development speed.
• 00:10:00 OutSystems discusses the true cost of technical debt, explaining that before implementing a feature, the team needs to have a good understanding of the feature, its value, and the context in which it will be used. The speaker then goes on to discuss how technical depth can be built up by understanding a feature on a functional level and then coding it without thinking about the architecture.
• 00:15:00 The video discusses the importance of having a good understanding of the feature being implemented in order to design the right architecture. It also highlights the conflict between business stakeholders and technical stakeholders, and how a lack of understanding by either group can lead to problems down the road.
• 00:20:00 The speaker urges designers to make their architecture visible in order to ensure that features can be delivered on time and without issues. It is important to keep in mind that technical depth (the amount of work required to deliver a feature) is always growing, making it harder and harder to meet client expectations.
• 00:25:00 The speaker discusses the difficulty of sharing technical depth concerns with clients, explaining that it is often difficult to deliver features while also avoiding technical debt. OutSystems offers a tool to help with this process, architecture dashboard True Change.
• 00:30:00 The speaker discusses the importance of having a technical stakeholder on the client side, and how connecting to a business value can be the most useful way to do this. If we are not able to connect the architecture to something functional, we may have problems with estimating and planning features.