Alternative Text by Jamie Dobson

When people ask me, ‘why Container Solutions?’, I always give the same one word answer: joy. When I was a kid I had a Commodore 64. It had a version of BASIC on it that I used to mess about with. I also played games on the C64. In both these cases feedback was quick. There are loads of reasons why this quick feedback is important, ranging from getting into flow to not having too much code in progress lying about. It was only when this quick feedback was taken away from me, in about 2004, that I realised my joy had been taken away, too. I started to dislike programming.

So what happened? In the early noughties I graduated from university and started coding professionally. A lot of this work was on web-applications and we used things like EJBs and Websphere. My job, therefore, was extended to include configuration management. This was good and bad. It was good because there was loads of scope for automation, which meant I got to program more. It was bad because the configuration nightmare never ended, no matter how much I could automate there was always some peculiar system that I couldn’t get access to and certainly couldn’t change. But it was bad for a much larger reason: it depressed me. I may have been at work all day programming, which usually made me happy, but the work I did was automating the build. Which meant I wasn’t actually doing what, as an engineer, I was supposed to be doing, namely, fixing problems for someone who cares.

It was in about 2004/2005 that I turned my attentions to returning the joy back to coding for myself and anyone else who I worked with. This is what led me to becoming a bit of a dictator in regards to our set up, our IDEs and way we treated each other. If we wasted time on configuring an IDE, we weren’t doing something valuable. If we wasted our time clawing each other’s eyeballs out, we weren’t doing something valuable. Now this no tolerance approach of mine was good training for my later work as a CTO and nowadays as the CEO of Container Solution. But… but. None of it was enough to return coding on my laptop to the joy I had coding on the Commodore 64. That would require a technological advance that didn’t come my way until January of this year.

Steve Case, who got a lot of people online before the web was even invented, took one computer science class at university because, ‘this was the punch-card era and you’d write a program and then have to wait hours to get the results’. But the thing is, years and years after punch-cards became obsolete, we were also waiting hours, sometimes days, to get the results of our latest efforts. And actually, right now in 2015, some of my customers have to wait a week to see the results of their efforts because their infrastructure has been outsourced to a ‘third-party vendor’ – i.e. a thief.

So what happened in January? We set up Mesos, Jenkins, Marathon and GitLab on Google’s Compute Engine. My interaction with the build now ends with ‘git push origin master’. Once I hit enter after typing that command, Jenkins, Docker, Marathon and Mesos all collaborate to take what I’ve done and put it in production. The whole thing takes less than a minute.

I don’t care what anyone tells me about their builds, there is nothing as smooth as what we have at Container Solutions. It is so smooth that I’ve actually started coding again and in a fit of enthusiasm invited people to my office to see how this magic works. What joy. I actually found myself smiling again.

1 Comment

  1. I’ve spent lots of time trying to discover what my source of joy is. The question came when I realized that joy is not something that can be controlled. Why did I want to control? Because honestly I lost for long time I could not find it back.

    It took time but I found out that my joy dwells in work that is of value for people. Probably that’s why the most impressive presentation during GOTO 2015 for me was a lecture given by Mary Shaw, where she defined engineering as

    creating cost-effective solutions to practical problems by applying codified knowledge and building things in the service of mankind.

    This reminded me this blog post:

    as an engineer, I was supposed to be doing, namely, fixing problems for a someone who cares.

    that’s why I am here again.

    Today I had a pleasure of having a chat with David Allen, the author of the Getting Things Done book. His saying was that engineers are in a unique position. They are able to help people building a space for creativity by automating tasks that are not creative. Well said.

    The source of my joy was hidden very deep, but I found it. At CS I started smiling. This still does not happen often, but I will keep on digging that well.

Leave a Reply

Your email address will not be published. Required fields are marked *