Skip to Content


Posted on 2 mins read

The founder of this company has asked me not to publicly identify them as they do not want to be included as a public portfolio piece.

When Mr. G approached me, the app they were building was in bad shape. Several poor practices had meant that it was struggling to stand up under minimal load. Serving their modest customer base had already become a problem. Initially, I worked to alleviate bottlenecks that were causing the app to falter, and add a couple of features that were necessary at the time.

From that point, it became clear that it was necessary to restart development. This is not normally a step I recommend, as throwing out a whole system means that lessons leant building that system are often forgotten. In this case, it was necessary.

We started from scratch and rebuild the first version of the app in around six weeks. From there, additional features could be added and the app was able to scale to their (at the time) modest needs. As time went on, we continued to add features, scale and update the app, and eventually it became obvious that a small team was needed to take over the day-to-day running of the site.

I helped Mr. G to select and interview candidates and we build out a team of four developers to take the company forward.

At the time of writing, the company is expanding quickly with many thousands of active daily users and scaling the app rapidly by extracting microservices and moving to a much more flexible architecture.

  • Ruby on Rails
  • ElasticSearch
  • Postgres
  • Auto-Scaling
  • Microservices
  • Team Building