The Two Codebases

I have been working on a project for a while. It’s a simple tool for running A/B tests on your links. You enter your link, and it generates a new one. You share this new link with your users. It tracks the clicks and shows you the results.

You can track the clicks of your links with the following filters:

• Operating System
• Browser
• Device

My tech stack was Next.js for the frontend and Nest.js for the backend. I built the frontend first, then connected them together. At first, everything was working fine, and I was happy with the results. But when I started the database, opened two different VS Codes and terminals, and started checking things on both sides, I realized I had screwed up.

The ugly part was that whenever I needed to add or update some code on one side, I had to do the same on the other side. It was a pain.

The worst part was when I encountered a bug; I had to check both sides to find the root cause. It was a nightmare.

One day, I decided to change the tech stack. I completely switched to Next.js and removed some of the features.

If you are a one-person team, you should choose a tech stack you are comfortable with. The first goal is to finish the project. You can always refactor your code later.