What makes you a good programmer?

If you ask 10 people this question, you will definitely get 10 different answers. Although the answers might be put out in different words, they would probably convey the same meaning. To me personally, a good programmer is someone who is capable of understanding the problem, coming up with a viable solution, being able to present that solution to the end-user in a feasible way and work as a team to reach this end goal.

But how do you manage huge code with so many people contributing to it?

Each contributing member is expected to write code that is clean and maintainable. Well, how do you do that? You follow certain coding principles. These principles make yours and the life of others easier.

The right tools to implement these principles

There are tools that make it easier to follow these principles and that, unfortunately, is not discussed as much as it should. My suggestion to you is — look for them! For example, frontend developers use cloud component hubs like Bit.dev to publish independent components.

How do they help in following these principles?

The freedom to publish components from any codebase means more code is shared and reused — following the DRY principle. It also means you don’t build a complete design system with UI components you’re never gonna use — instead, each component gets built and published only when it is needed — following the YAGNI principle .

It also means you don’t build a complete design system with UI components you’re never gonna use — instead, each component gets built and published only when it is needed — following the . Building components as independent pieces of code, intended to be published, reused and collaborated on (as independent code), naturally makes each developer more mindful of the single responsibility principle.

Exploring published React components on Bit.dev

Here are four coding principles every programmer should follow.