> As far as scheduling to tackle the tech debt, work toward including it in the requirements for future work. You must address X to build Y, etc. Addressing technical debt as a project that leads to no new end result (eliminating toil is one), has little (but not zero) value.
This advice is very actionable, I'll try it out, thanks for the tip!
Sorry that I present myself to be critical to the team, I am not and I am impressed with how much they achieved given the time frame. In fact, all of the team are in agreement on most of the issues, but I am not entirely sure what to prioritize and how to balance it with the regular feature work
It depends on project size, twitter likely have some really huge scala project, but many organization are now going for microservices, so compile time is less of an issue
