I think this is company culture. You're asking how to make your engineers give enough of a damn about their output to spend the extra time understanding it.
Did they do this before AI? Does the company really, truly care about software quality or are they just trying to ship features?
Things like
- in depth code reviews
- encouraging sharing knowledge and helping others
- dedicating time to address technical debt
- giving engineers freedom to explore technologies and solutions
- following best practices for software dev
- hiring the right people
This is one of those things you can't enforce, but your leadership can encourage it by setting examples. If your company does not care about understanding the software by carving out time and explicitly encouraging it, then employees won't either.
Did they do this before AI? Does the company really, truly care about software quality or are they just trying to ship features?
Things like
- in depth code reviews
- encouraging sharing knowledge and helping others
- dedicating time to address technical debt
- giving engineers freedom to explore technologies and solutions
- following best practices for software dev
- hiring the right people
This is one of those things you can't enforce, but your leadership can encourage it by setting examples. If your company does not care about understanding the software by carving out time and explicitly encouraging it, then employees won't either.