5 things I wish I knew before starting serious development (a journey into code perfection)

The article says that writing code that works is only the starting point. Clean code takes more care, because code is read far more often than it is written, and quality choices pay off over time.

Reading notes

#

• Choose names for functions, classes, parameters, files, and folders that show purpose, usage, and behavior, so the code explains itself.
• Avoid unnecessary comments, because code should usually carry its own meaning; keep comments for TODOs and for decisions that need context.
• Keep formatting consistent with the project or language rules, since readable spacing and indentation are part of code quality.
• Keep functions short, focused on one thing, and at one abstraction level, and split them only when decomposition makes the code easier to understand.
• Treat code as shared work, improve old code when you touch it, and review the code rather than the person who wrote it.