Managing Technical Debt with Clean Architecture & Clean Code

In today’s large scale, rapid and ever changing software systems, it’s not possible to be perfect all the time and that’s okay. The problem arises when we’re not unaware and/or unable to handle the situations that arise out of it.

The idea of clean code and architecture is to help you to not to get into the situation where you don’t have any control over the system and this session is all about how to make use of them effectively and efficiently.

Key Takeaways:

1. Understanding the rationale behind clean code & clean architecture.
2. Technical debt and the reasons behind it.
3. Handling technical debt immediately & later
4.Technical debt and scaling of the software
5. The impact of Test Infrastructure in maintaining software sanctity