<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adam Butler on Medium]]></title>
        <description><![CDATA[Stories by Adam Butler on Medium]]></description>
        <link>https://medium.com/@adambutler?source=rss-b47822d08c3a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OV8iN4VJXkJLm5RR.jpg</url>
            <title>Stories by Adam Butler on Medium</title>
            <link>https://medium.com/@adambutler?source=rss-b47822d08c3a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:40:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adambutler/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[One hundred days of open source]]></title>
            <link>https://medium.com/@adambutler/one-hundred-days-of-open-source-ade0d9e48dd4?source=rss-b47822d08c3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ade0d9e48dd4</guid>
            <dc:creator><![CDATA[Adam Butler]]></dc:creator>
            <pubDate>Tue, 20 Jan 2015 22:07:19 GMT</pubDate>
            <atom:updated>2015-01-20T22:20:20.646Z</atom:updated>
            <content:encoded><![CDATA[<p>I have no idea how to build a website… <em>well not really</em>. The thought of building, publishing and launching a website end-to-end without using any open source component, be it Nginx or Ruby-on-Rails, let alone the operating system, seems like an impossible task to me. I expect most web developers would say the same; at very least those born from the eighties onwards.</p><p>The reason for this is that we rely on building blocks and these blocks allow us to write our intentions in a far abstracted manner. Looking at a typical web application this might consist of a web server, an application engine and a database, all of which have their own dependencies in a seemingly infinite cascade of reliance, hitting rock bottom only deep at the hardware level.</p><p>Most of this stack happens to be open source and without it we couldn’t dream of building the kind of sophisticated software that we have come to expect today. I believe giving back what you can to open source is really important and through doing it myself I’ve become a more rounded person by working to other peoples ideals, made new friends and have been involved in the success of various projects that I use myself and love greatly.</p><p>I want to tell the story of my first one hundred days of an experiment with making everything I build open source. Naturally I will start from the beginning back in the days when I was doing Flash websites. At this time I was deluded into the assumption that if I gave away my work someone was bound to steal it and make their fortunes from it.</p><p>Fresh out of university, I, like most of my peers. had a huge bank of ideas for new projects, each one more exciting than the last. This almost always led to these projects being dropped in favour of the next. I was left with a hundred or so half-baked projects ranging from a server manager to an iPad game. I always found myself doing the bit that I found fun and then getting distracted. It wasn’t all a complete waste of time though, beyond keeping myself entertained I was also learning and working out what I wanted to do with my life.</p><p>A couple of years ago I started learning Ruby-on-Rails. I specifically wanted to build a web application called <a href="http://conduct.io/">Conduct</a> that allowed you to create questions and make group decisions quickly and easily. This was a product that I wanted to use myself, for arranging meetup talks, but I couldn’t find anything that matched the elegance of what I planned to build. I set out developing the application and enforced a ban on myself to see the project through to the end… eighteen months go by and I’ve not shipped. I’m frustrated and worst of all I’m not learning anything new.</p><p>It was around this time, in August 2014, that I broke my rule. I had a server root password that I needed to send to a someone via our client and I wanted a way to do this as simply as e-mail but as it was only on a local network it wasn’t necessary for this message to be encrypted. I wanted to build something <em>just</em> slightly better than asking someone to delete the email after they read it.</p><p>In my lunch break I quickly threw together a Ruby-on-Rails application called <a href="http://kevlar.io/">Kevlar</a>, basically snapchat for text. I quickly threw it up on Heroku for ease and made it open source. I loved this little project, it was simple, required no registration and did one job well. Over the coming weeks I iterated on it, shipping often, it was a refreshing change.</p><p>About five weeks later I broke my rule again, I tried using <a href="http://www.polleverywhere.com/">Poll Everywhere</a> at an event I was running but its promising well designed front-of-house doesn’t quite propagate into the application itself. The application also required registration, which for my purposes wasn’t necessary. I decided to build <a href="http://poll.lab.io/">Poll</a>, an application to run polls simply, without registration and in realtime. I now had two little projects I was maintaining on a daily basis and each day I embraced making atomic changes that allowed me to deploy regularly. It was awesome to see people actually using it, a French university even ran their student elections on it.</p><p>I’ve always found the best way to learn something new is to challenge yourself, sometimes literally putting your own assumptions or beliefs to the test. Only a couple of months ago I had a bias against HAML because of other peoples opinions, but after challenging this bias I’ve come to love it and am now using HAML in most new projects. Taking the same approach I ran my open source experiment by forcing myself to ship open source everyday, starting by setting myself a few new rules -</p><ol><li>Do something every day that is or will be open source</li><li>Leave it better than you found it</li><li>Ship early, ship often</li></ol><p>The work I do every day can be as small or as big as I like but I like to ensure it’s always wrapped up in the same day; if it’s better than I found it then I will usually ship it, even if it has known bugs.</p><p>With my long term project Conduct I found that the application was never at the level of quality that I was happy to launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*QQVEoj2-UFiSnxvMLXzKRA.jpeg" /></figure><p>One of my concerns stopping me shipping was the imperfect mobile responsiveness. In contrast, when I built Kevlar I shipped regardless of the lack of any mobile optimisation because a bad mobile interface is always better than no interface at all.</p><p>In November I started to contribute more to other peoples projects, mostly modules that I consume but also projects like <a href="http://24pullrequests.com/">24 pull requests</a>. I also started digging through my hard drives looking for projects that I could release. I often build tools for myself and found some gems like <a href="http://orientation.lab.io/">orientation</a> that had no reason to be closed source at all. I even eventually got back to <a href="http://conduct.io/">Conduct</a> and with my refreshed attitude just launched and open sourced it. Turns out unlike Kevlar and Poll nobody uses it, hence<em> rule #3 ship early, ship often; </em>you never know if something is useful until you test it with real users.</p><p>With my new projects I started open sourcing before I even wrote a line of code. This stopped me from even taking into consideration of when the project was ready for other peoples eyes.</p><blockquote>Quick tip: Git allows you to do empty commits with -<br>git commit -m “Init project” —allow-empty</blockquote><p>More recently I started working on the website for our upcoming wedding. I wanted it to be a tool that took RSVPs, managed guests and tasks, calculated costs and accepted photo uploads. For the last couple of months my efforts have been mostly focused on building this project, which you can find on <a href="http://github.com/adambutler">my GitHub</a> as wedding-on-rails <a href="https://github.com/adambutler/wedding-on-rails"><em>source</em></a><em> </em><a href="http://hitched.it/"><em>demo</em></a><em>.</em></p><p>Finally my latest venture is <a href="http://github.com/adambutler/alfred-workflow-package-manager">Alfred Workflow Package Manager</a>; if you’re looking at getting started with open source I’d love it if you stop by and contribute :-)</p><p>All of this has completely changed the way I work in both my side projects and in my day job. I don’t think finding time for open source <em>every day</em> is sustainable. It interrupts me from other priorities and I’ve been writing less since starting but for now I’ll continue to do it when I can.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ade0d9e48dd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My all time top productivity hack]]></title>
            <link>https://medium.com/@adambutler/my-all-time-top-productivity-hack-d6b7b944a975?source=rss-b47822d08c3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6b7b944a975</guid>
            <dc:creator><![CDATA[Adam Butler]]></dc:creator>
            <pubDate>Fri, 10 Oct 2014 14:27:40 GMT</pubDate>
            <atom:updated>2014-10-11T13:10:46.603Z</atom:updated>
            <content:encoded><![CDATA[<p>Stop reading productivity blog posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6b7b944a975" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I connected my Coffee Machine to the internet ]]></title>
            <link>https://medium.com/@adambutler/why-i-connected-my-coffee-machine-to-the-internet-bd0c1546c03c?source=rss-b47822d08c3a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd0c1546c03c</guid>
            <dc:creator><![CDATA[Adam Butler]]></dc:creator>
            <pubDate>Sun, 13 Jul 2014 11:34:31 GMT</pubDate>
            <atom:updated>2014-07-13T18:21:08.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>And the most odd bug I’ve ever fixed.</h4><p>As a child it wouldn’t be an uncommon sight to see me taking things apart in an attempt to try to understand how things worked, this was usually to my parents disliking as I rarely managed to reconstruct the appliance. I must have broken more than a dozen toys, computers, games consoles or just anything else with movable parts, a motorbike included. I don’t think this is atypical for most developers, our career choices inherit from a fascination with problem solving and the excitement that comes through solving them. I’ve not yet met a developer who would turn down a challenging task over one they feel perfectly comfortable with.</p><p>Another interesting observation is that developers are commonly workaholics. Every job has its highs and its lows, sometimes you’re the “Ninja Developer” that shipped twenty awesome new features before lunch and other times you’re maintaining projects day dreaming about if the <a href="http://en.wikipedia.org/wiki/Infinite_monkey_theorem">Infinite monkey theorem</a> would also apply to the job you’re working on that day. These are the days I’m almost certainly hacking away until the early hours of the morning, because like a junkie after a weekend of going cold turkey I need my fix.</p><p>The work I do in my spare time is never for profit, and in fact commonly comes at a financial cost to myself, but it’s rewarding, fun and most importantly I get to learn something new. I’ve increasingly found myself working on hardware projects over the last couple of years, it’s new territory for me and I don’t know if it’s just the manifestation of my code in the physical world but there is something extra special about getting something physical to happen rather than just pushing pixels.</p><p>The first hardware project I worked on was perhaps the only practical one I’ve ever done. I was working as the only developer for a footwear company, if I was on holiday I’d have to find a machine to log into every Friday and deploy a feature to the homepage. This was co-ordinated with e-mail and social campaigns and often required last minute changes which made it too risky process to automate. So I built a big red shiny button to do deployments. Nothing was easier and it ended up being the process for deployment even if I had a shell running right in front of me… I mean after all who could resist hitting a big red shiny button. The first build worked well but the button went through some practical and far more impractical variations, one such being that it played the one-hit-wonder Friday song by Rebecca Black during deployments.</p><p>The next project was after I moved to an agency called Simpleweb. At Christmas we did secret santa where the presents were all bought from local charity shops.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wxEYFI7z0Uj31yrKLBYTyg.jpeg" /></figure><p>One of the developers got a gum ball machine style M&amp;M dispenser which within a week I had wired up a servo and a RaspberryPi which ran a Node.js application to dispense M&amp;M’s whenever a new feature was completed and merged into the projects `master` branch.</p><p>This was a lot of fun, it taught me about Servos, setting up a RaspberryPi, familiarised me with the GitHub API and gave me some playtime to hack away with Node.js. As a bonus at this time I was also learning <a href="http://coffeescript.org/">CoffeeScript</a>, since this wasn’t a critical project it gave me a platform to experiment on without too much concern of breaking anything important.</p><p>Following this I built several other hardware based projects — A Kinect powered turret based on my favourite game Portal. — A bird box camera trap and I’m currently working on a Leap Motion powered robot built out of the shell of an old vacuum cleaner. My favourite project however has to be my RESTful power plug.</p><p>I’m usually the first in the office and admittedly I’m a grumpy sod until at least my second morning coffee. I wanted to rewire our office coffee machine and build an application that allowed me to start it brewing before I arrived to work. A timer wouldn’t work well as sometimes I’d arrive at 8am whereas other times it wouldn’t be until 9am I needed to devise something smarter. The original plan of rewiring the machine was quickly dismissed as I didn’t want to break the machine, non-caffeinated developers can be mean! Instead I opted to modify a power strip to turn the source power on and off instead, this had the advantage of making it portable and could be repurposed for any occasion.</p><p>I started out by stripping down a typical four socket power extender and quickly discovered that I wouldn’t find a easy or more importantly safe way to mount the relays that would control the power supply. I then discovered that you could get plastic boxes that wall sockets screwed into called pattress boxes. A 55mm box provided me plenty of room for a heavy duty four channel relay.</p><p>Now, I haven’t yet mentioned short of GCSE level electronics I don’t have any formal electrical training. This was the first time I’ve worked with high-voltages. This wasn’t a problem however plugs and relays are the bread and butter of the electronics, nonetheless I planned, then I planned some more and then I tested my circuit against not one but three schematic tools just to be extra sure I’d wired everything correctly. Furthermore I used certified cables and my relay was rated up to 10A well more than I would be consuming.</p><p>I wired plug mostly as normal but instead routed the live via the relay, which is basically a magnetic switch that is controlled by a 5 volt bridge between it and a RaspberryPi. The first test I built allowed me to control the RaspberryPi GPIO pins, and therefor the relay over SSH, it was ready to test. At first I wired up a lamp and it worked first time. To say I was excited was an understatement. I could trigger the lamp on and off from across the room… yes I really was <em>way</em> across the room, with a fire extinguisher to hand just in case.</p><p>Shortly after this I built a Node based RESTful interface which not only allows me to turn the sockets on and off but also allows me to run a socket for a specific duration. The beautiful thing about doing this as an API was that it allowed nearly anything to interface with it. Within two hours I could control it with SMS with the help of Twillio, I could use a OS X program called <a href="https://medium.com/">Alfred</a>, I could control it though the web browser and I could trigger it with my <a href="https://getpebble.com/">Pebble smart watch</a>.</p><p>This brings me onto the most interesting, ironic and weird bug I’ve ever had. At Simpleweb we track out application bugs on a system called <a href="https://bugsnag.com/">bugsnag</a>. Any time a site breaks we get notified with an e-mail. We have regular hack nights and for our halloween hacknight I wired the plug to a lamp that was fitted into a pumpkin. Among other implementations, every time bugsnag threw an error the pumpkin would light up and not so spooky sounds would play from it. I forgot about this… at least up until last month.</p><p>I’ve had the plug wired to the coffee machine now for a while and it’s been rock solid reliable when I want to trigger it, however sometimes it would mysteriously turn itself on. I just assumed it was rebooting itself occasionally and thought nothing of it more than I should fix that at some point. A couple of weeks back I got an e-mail from Twilio informing me my credit had run out… How I thought, I’ve not used the SMS trigger in months. Looking at the logs I could see lots of messages containing the body message “On” from a US number, who was doing this I thought and why? Upon goggling the number I realised it belonged to <a href="https://ifttt.com/">IFTTT</a> a service that takes an input, in this case an e-mail from bugsnag and produces an output, again in this case an SMS to Twillio to turn on my plug. So yes, every time a website of ours crashed I was accidentally brewing coffee, but lets call it a feature.</p><p>All these projects have been a lot of fun and very interesting, this project though due to it’s RESTful interface gave me an opportunity integrate into lots of different platforms and keep hacking away. Let me know you’re thoughts and ideas in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd0c1546c03c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>