Modern software development is full of useful tools. The challenge is that every tool also creates a decision: when should it be used, who maintains it, and what does it make easier to misunderstand?
Clarity is a technical advantage
Clear interfaces reduce the things a team must remember. Clear names reduce the context a reviewer must reconstruct. These are not cosmetic improvements; they shorten the path between a question and a correct answer.
I prefer visible data flow over clever indirection, treat review as a design conversation, and measure the cost of an abstraction before adding it. Those habits keep the code understandable as the tools around it change.
Good engineering makes the next change easier to think about.
Those habits survive changes in frameworks and platforms, which is why they remain worth practicing.