Technologies and frameworks change, but architecture principles, and best practices in writing high quality code have remained the same!
Here is a LinkedIn post that I posted a few days ago, and decided to write a follow up article on what I think are the best practices to build high quality software today!
Adhithi Ravichandran on LinkedIn: #software #architecture #coding #technology | 11 comments
6 years ago I was coding in C++ and Java. Today, I don't know anything about what's going on in that space! I code in…
Here are the best practices that I would focus on while building high quality software:
1. Don’t Over-Engineer
Lot of the times, architects tend to solve problems that don’t exist today. This is not necessary and you will end up with a cobweb architecture and code that was designed for the future use-case that may never happen!
Over engineering results in unnecessary abstractions and results in complex code. Although you want your code to be scalable in the future, designing for the future and abstracting away for future use-cases is not the ideal way to architect your software. Shipping high quality software within a reasonable time frame is of utmost priority, and architects need to solve the problems that the market/end user is facing today. Stick to the requirements of today, without trying to solve complex problems of tomorrow.
Solve only the problems that you have today!
2. Modular Code
It is important to keep in mind the separation of concerns while architecting your software. Break down the system based on different functional areas into independent, interchangeable modules. This results in modular code with well defined areas.
Some of the common techniques in writing modular code are: