We spend more time reading code than writing it. So if the code is more readable, it will obviously increase developer productivity.
Many people associate the readability of code with coding conventions like following standard naming conventions, closing files, DB resources, etc. When it comes to code reviews, most people focus on these trivial things only, like checking for naming convention violations or whether resources are properly released in a finally block.

Test

Code readability goes beyond naming conventions and formatting. Mixing different abstraction levels in a single method makes code hard to read and maintain. Using a fund transfer example in Java, the post contrasts a monolithic method that mixes JDBC code, business logic, and exception handling with a refactored version that separates concerns into distinct methods and DAOs. The clean version has a high-level orchestration method that reads like business requirements, with implementation details delegated to focused private methods and data access objects. This separation makes enhancements easier to locate and implement.

Clean Code: Don’t mix different levels of abstractions