• Balancing between "perfect" and "broken".

    Last week I found very lame and stupid bug in Groceryx. I've made a huge mistake when I was designing the data model. When designing UX for app's first launch I wanted to give users some set of predefined items to show a sample shopping list and to make suggestions when adding a new item to the list. Here is how my simplified data model looks like:

  • The joys of automated app deployment for a one-man shop.

    Last week I wrote about why I automated server provisioning for Groceryx. Today I want to share with why it is important to have automated deployment process of your app even if you a one-man shop. By the app in this blog post I mean the backend part of your app, one that is deployed on your server.

  • The joys of automated server provisioning for a one-man shop.

    When Groceryx was merely an app idea I knew that I am going to need a server backend for it. Although it was a one man project, I've decided not to cut corners and invest some time in automating server provisioning and app deployment. Just to understand what are the benefits.
    First I needed to choose what tool I'll use for that. The industry standard Chef and Puppet I found them quite an overkill. Their usual configuration has a dedicated server for just running Chef or Puppet. I wanted something simpler that I could run on my laptop. My primary requirement for this kind of tool was idempotency.

subscribe via RSS