Choosing a Tech Stack for Software You Sell: Experience Over Trend

Headline reading 'Developing is the easy part. Maintaining is harder.' with the labels Tech stack, Experience and Maintenance

One of the most popular debates, especially between developers, is: what is the best language, framework or stack? Everyone will promote their preferred one, and some will even walk through fire for their stack.

It all depends on context

When choosing a tech stack, it is important to acknowledge a few factors. It all depends on context: who is the one developing, for whom, what, where and what is the capacity. While some languages are better for some things, when it comes to building systems you want to sell, jumping between frameworks is rarely practical.

You sometimes have to build on your knowledge and experience to create a product which is reliable and has experience behind it.

Don’t be ashamed of your stack

Sometimes people will look down on you for not using the new trend or the next fancy framework. In reality, if you are doing this yourself, there are many things to consider before investing the time and effort into a new framework or language.

Starting with a new framework means learning the ins and outs, so you will face issues and bugs you would not in the language you are familiar with. Then there is maintainability: suppose you go fancy or trendy, how do you keep up with different code bases or frameworks to make things work?

Developing is the easier part of it all. Planning is hard. Maintaining and scaling is much harder.

Build on a foundation

As I have progressed in my developer life, I now try to upgrade myself on the frameworks and skills I am familiar with, to build on a foundation. That matters most when it is a product you are selling and you have clients. Passion projects are okay for experimentation, but an existing system should not have amateur bugs or issues because you decided to do something new for the sake of it.

What is the trick? Learn different languages for different purposes and build on them. If you are a Python person for scripting, build on that and do not switch to another language for scripting. If you do ASP.NET for web apps, build and improve on it. Switching to React out of nowhere is just a recipe for trouble.

Real life is different from theory

Real life is a lot different from theory, and I no longer think there is a best language. It is case by case, and your experience and skillset highly impact and determine the “appropriate” language, especially when it comes to something you are selling.

I wish someone had told me this a lot earlier. I spent a lot of time trying to learn new frameworks (not successfully lol), and it gets demotivating very soon and you end up doing nothing.

Want a system built on tools we know inside out?

One Click Solutions builds reliable software and automation, in plain language. The first 15 minutes are free.

Book a free intro call

Discover more from One Click Solutions

Subscribe to get the latest posts sent to your email.

  • Share:

Leave a Comment

Your email address will not be published.

You may use these HTML tags and attributes: <a href=""> <abbr> <acronym> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Send a Message

Discover more from One Click Solutions

Subscribe now to keep reading and get access to the full archive.

Continue reading