> forced to adopt the coding style and practices of that legacy project Let's keep going with this SQL-injection prone legacy framework, with zero automated t

> forced to adopt the coding style and practices of that legacy project Let's keep going with this SQL-injection prone legacy framework, with zero automated tests for the entire codebase! I've hit that, for real. Sometimes you really do need to move mountains to change legacy.