Guest post from Paul:
I’ve always been keen on simple tech. Simple ideas executed well. I’ve always had a passion for clean ideas and clean design. Obviously Story is all of these things. Or is it? I thought so but when you lift up the hood…
I have a 30 minute train ride into work each day. When I’m not coding, I fill these 30 minutes very easily thinking about what I need to do and what decisions need to be made to make a minimum viable version of our app. It was overwhelming at first. Everything from Amazon S3 bucket naming conventions to authentication methods were consuming my thoughts. There is an abundance of tools and frameworks and platforms I should and could develop this app on too, each with their own advantages and disadvantages. Which church do I worship at? Python, Rails, Node, PHP? MySql, PostgrSql, NoSql? Yii, Django, Codeigniter, Zend Framework? .NET? Joke. Eventually I left that candy store behind and decided to play to my strengths. Lightweight MVC PHP framework and MySql to build a RESTful API, Amazon AWS to handle hosting, storage, CDN, emails and a Github repo in a pear tree. This doesn’t seem a bad start to me.
What could go wrong? Well a number of things I guess. Will it scale? Yes and no. Will there be performance issues? Hopefully not. Should I care about these right now? Yes and no. I feel (maybe naively) that at this point there is no problem I can’t overcome by chucking virtual machines at it. Having a nice flock of EC2 instances to handle any load actually makes me feel quite warm inside. So far, everything feels nice. My API is returning sweet little nuggets of json for consumption. I guess at this point that is all I can ask for.
I’m sure at some point we will employ someone who will look at my little “spice rack” and shake their head like you do when your dad is making Ikea furniture. That will be a good day. In fact, I might take my little spice rack to some tech meetups and give it an airing.