DEV Community

Fagner Brack
Fagner Brack

Posted on • Originally published at fagnerbrack.com on

Popular !== Useful: The Case for Smart Software Development

Popular !== Useful: The Case for Smarter Software Development

In programming, what’s popular doesn’t necessarily equate to what’s best. The reason for this is simple: economics. Society rewards those with the reach and influence to make things popular rather than those who create useful solutions based on merit. This often leads to a situation where the programming tools and techniques that are widely used are not necessarily the best fit for the majority of use cases.

Take Facebook and React as an example. React is a popular choice for building websites, even when it’s not the best fit. People often choose React because it’s associated with a successful company rather than because it’s the best tool for the job. But the success of a company like Facebook is largely unrelated to the technology they used; it’s due to their business product and market fit.

This is an interesting take on the issue, although I'll try to focus more on the potential solutions.

So, what’s the smart way to develop software? It starts with building a strong foundation of knowledge within your team. Gathering people with different experiences and a broad knowledge of available tools and techniques can provide more options to solve problems as they arise. Over time, your architecture can evolve to incorporate new tools and technologies if and when needed, rather than starting out with everything from day one.

The smart way to develop software starts with building a strong foundation of knowledge within your team.

A modular approach is one key to building software that is easy to change and delete. Building components that are separated ensures that changing or deleting one component will not break another. This also means that your code is more easily adaptable to change in the long term.

On the other hand, it’s important not to ignore the value of tooling when it’s needed. Failing to use the right tools can lead to issues such as over-engineering, but doing nothing when the situation calls for it can lead to a prototype becoming the permanent solution.

In short, the key to smart software development is knowing what’s popular but not blindly following the crowd. Instead, build a foundation of knowledge within your team and make decisions based on merit rather than authority or popularity. By building a modular architecture that is easy to change and delete, you can adapt to changing circumstances and ensure that your tool is always the best fit for the job.

Thanks for reading. If you have feedback, contact me on Twitter, LinkedIn or Github.

Top comments (0)