My team’s coding standards and best practices

“Knolwedge is a treasure, but practice is the key to it”

— Lao Tzu

An engineering team can be a high performing one if there’s a consensus between them in how they write quality code, standards and best practices they believe in and follow.

These are the coding standards and best practices adopted industry-wide and made sense for our team. But none of them are strict. Developers have to choose them wisely based on the requirement and can discuss with the team.

Keep SOLID principles in mind

Writing loosely coupled, highly cohesive code is much appreciated. SOLID principles make the code more manageable, testable and maintainable.

Reference: https://www.baeldung.com/solid-principles

Apply design patterns when and wherever required, of course not overdoing it

Whenever there is a potential recurring problem, think of appropriate design patterns from GoF. Design patterns should make code easier to change, enable clear and effective communication across the team.

It’s also important to discuss design patterns during the design phase and the team agrees to it…