Sitemap

Growing Pains

Waking Up a Little Taller Every Day

3 min readMar 24, 2014

--

It was in early 2006, I remember it well. I had just paid a pretty massive premium on ebay (I am most ashamed to admit) to get my hands on an elusive Xbox 360—as a side-note, I actually waited in line for a few hours to get one of the eighth-generation consoles: it seems I am getting cheaper with age.

Anyways, I had sold my Xbox and after a couple of hours playing Perfect Dark Zero (most dissapointing), I remember thinking I still had one value that wouldn’t fail me: Halo. I popped in the disc… And I discovered I had played Halo for the last time when I sold my Xbox (it turns out a software update would have fixed this issue but no matter). It is in this cruel twist of fate that I learned of backwards compatibility.

In the first few months of our building Shout, Zach and I were intent on getting a product out as fast as we could to learn from actual interactions with people. Our actual product work had been prefaced with our both picking up the technologies we wanted to build our mobile and web back and front-ends with, and we were kind of sick of reading through manuals I reckon. Thus, with an early feature-set in mind, we built a product that was “good enough” for us to start experimenting and learning.

Get Shout’s stories in your inbox

Join Medium for free to get updates from this writer.

As things progressed and Shout grew, with Wes, we were happy to focus on building new functionality in line with Shouters’ demands, on tweaking product flow and changing up product-facing features to keep a sort of momentum going. Today, I’m really happy to say this can’t go on.

With our team growing (thinking of you Connor), and our user-base expanding, we’ve reached a point of no-return it seems in which a decision must be made. Our vision for Shout has changed tremendously in the past 8 months, and the product we first built has reached its limits in terms of how flexible it had proved. We wanted to build and build fast, and so we did. But today, as we have found our focus and with our user-base and intellectual capital far exceeding our product’s quality, it is time for us to lay roots.

This week and next, we will complete the overhaul of Shout’s backend, to commence the transition into a new version of Shout that will prove more scalable and flexible to work with, and allow us to move much faster for our users without ever having to sacrifice quality for speed. I believe we could have come to this crossroads later if we had built the product out feature-by-feature (we started off building the entire API because I still didn’t know iOS and we wanted to build proper endpoints) which would have made for more modular code… But I’m pretty thrilled we’re here. While our first refactor may require a quick update from our users, I really believe this will allow us to deliver a much higher quality product.

We’ve learned so much in the last few months, and we’re really excited to show you that as we prepare to push Shout in a much bigger way.

Henri

Here’s to looking at you, database redesign.

--

--