I recently heard of a new "AI" based tool for developers that can explain both what a piece of code does and why.
The claim about "why" can easily sound appealing, but it is very open to misinterpretation.
It may be possible for the tool to explain why the code works, but it can't explain why the code exists.
It can't say why this code is the best way to solve the problem it exists to address or what the person using the software is trying to achieve.
It's necessary to know more than just the code to understand why software exists and what it does for the people who use it.
I know developers (and many companies) don't want to hear it, but it's necessary to record (document) more than just the code.
