Our company never adds comments, because the code speaks for itself.
And with genAI I can have these comments added in very low time, helping me to get an overview of what happens.
But as for the "why are are doing this in the first place" business documentation is usually outside the source code and therefore out of reach of any genAI, for now.
As for what senior devs should do when coding:
> They're constantly:
> Refactoring the generated code into smaller, focused modules
> Adding edge case handling the AI missed
> Strengthening type definitions and interfaces
> Questioning architectural decisions
> Adding comprehensive error handling
Ain't nobody got time for that! The one girl and other guy that could do this, because they know the codebase, have no time to do it. Everyone else works by doing just enough, which is nearly what TDD dictates.
And we have PR code review to scrape up quality to barely get maintainable code. And never overcomplicate things, since writing code that works is good enough. And by the time you want to refactor a module three years later, you would want to use another data flow style or library to do the work altogether.
