Should We Build

A tool to help you decide, to build or not to build?

Visit Website
June 2020 Finished the first version

It took a week to build this first version of "Should We Build".

I worked mostly nights and weekends, and I coded the whole thing in using next.js, react, and mobx. In hindsight, I realized that parts of my flow with mobx takes too much time.

Time spent:

  • 3 hours for the implementation
  • 3 hours to integrate the design, and build the visual parts,
  • 1.5 hours setting up the projects, domain name, and release.

Comment

June 7, 2020 Hired a Designer & Came up with the design

One of my goals is to build to project quickly and enhance my workflow.

For this side-project, I hired a freelance designer I worked with to come up with a design I can implement quickly. I'm glad I did: I spent much less tinkering around the design. And went straight to implementation.

Comment

June 5, 2020 Came up with the project

In my daily job as a Freelancer, I spend a lot of time helping my customers come up with their tech-stack. One of the main questions is, "Should we buy this service or build it ourselves."

I started working on this project to provide a simple interactive framework to let my customers, other engineers, and I come up with the "right solution."

Comment

About

For freelancers, engineers, and decision-makers. This app helps make a decision regarding your technologies and infrastructure. Should you buy a service or build it yourself?