Summary

If there’s one lesson to take away from this chapter on technical debt, it’s that asking the correct questions at the correct time can help your team build a platform that’s designed to last. The platform may never be finished. There will always be improvements to be found and gains to be made. However, a polished process for managing the platform and its corresponding documentation will allow the team to sustain it while maintaining the team’s health.

As you’re tackling technical debt, remember the example indicators and questions we discussed in the introduction to this chapter. Spotting technical debt and knowing the corresponding costs will allow you to better communicate and prioritize addressing those items with those teams that need to address them. While addressing technical debt is time-consuming and costly on its own, it will help you set the foundation for a platform that can last and is ready for future changes.

In the next...