What to Look Out for Before Choosing a Stack for a Project

There are a lot of libraries and frameworks out there. They are mostly designed to make work easier and faster, but sometimes they end up making you work slowly and feel frustrated. Libraries and frameworks still serve their purpose; you just have to use the right one for the right project. Here is what to consider before choosing a library:

The Stack: Is it just frontend, backend, or full stack? For instance, if you will not be needing a server, Next.js may not be your best option. Bootstrap can achieve that.

External Library: If you will be using an external API in your project, you need to read the documentation and be sure it will work with your framework. Recently, I was working on a messaging app. I chose Next.js because I felt it would be faster. Everything was working fine until it was time to use socket.io. Then I found out it’s not compatible, which was frustrating. Be sure your external API will work with your library.

Stable Framework: It’s hard to find a hundred percent stable framework as they update their components from time to time. That’s a good thing, but sometimes it breaks your code. Some are stable to the extent that when they update, the old version still works. Tailwind, for instance, is designed in a way that your code will never break.

Comfortability: It’s best to work with the language, framework, or library you are most comfortable with and which you are good at. Doing that will make you code faster. I, for instance, prefer not using TypeScript because it slows me down.

These are some of the few tips I learned on my tech journey.