With engineering rigor. They are fantastic tools for quickly navigating large codebases, ingesting large amounts of data, refactoring legacy code, compiling multiple formats of data, following defined patterns, and many other proper uses for the tools.

That doesn’t mean the code/result doesn’t still need to meet our engineering standards.

> Hopefully the people who feel that way are already close to retirement, so the choice won't have to be made for them.

One of the best ways to deal with doing something the wrong way is to get rid of all the people who know how to do it correctly. That way no one knows any better, so no one has to confront the fact they're actually doing it wrong.