Lewis Goddard

Currently working full-time as a technician while studying Computer Science at Open University.


I have written papers on things from capitalism and competitive economy in socialism, to the exaggeration and focus of historical views, and on to the equality of persons, or lack their of, and the restrictions of achievement for individuals (hard work doesn't get you everything, and practice won't always make perfect).


After joining eustasy early in 2011, I assumed control over the organisation in 2012. Since then it has grown from just half a dozen young developers to and average of 25-35 individuals creating code and designs using centralised resources every month. Much of the development from early 2013 onwards has already been open-sourced, with further projects being released as licensing allows. Starting from 2014, we have also opened up internal workings to quarterly review, in an effort to improve transparency and trust.

In 2014 - Year in Review, it is detailed how my management of the 103 contributors throughout the year has lead those wonderful people to help well over 10 million others, from 237 countries. That's more than 1 every 3 seconds. We also saw visits from countries like Svalbard and even North Korea, despite near total lack of internet access in these countries.

Proposals for next year include acquiring a server and SSL certificates for every site, and opening up a vote-spending option to claim rewards like server time, domain names, SSL certificates, and office and adobe subscriptions. A note to aspiring web developers looking to join: Less than 2% of our visitors use Internet Explorer, and we do not support anything but the latest version of any browser.

Open Source

I have two bad traits:

  1. I am selfish.
  2. I am controlling.

These are very good for one simple reason: When I cannot find a software solution to my problem, I write one. Then I maintain it.

I have worked on, as of early 2015, 47 projects. Of these, 12 were paid and private, either as one offs or part of some larger contract of employment, and 30 were personal. Of these, most of my personal projects get licensed under MIT and handed over to eustasy, where they can be maintained long after I am have moved on.

Just 5 things I've worked on have been directly to contribute to other projects, and only when I have already received a benefit from them. Typically, when working with a larger organisation, it is building a website to support elements of much larger endeavours towards improving peoples computing experience. I've worked with the passionate designers and developers behind elementary OS, and pushed previously (largely one-person) projects like DeVeDe and Midori into the the modern age.


Aside from constructing many of the eustasy projects and enterprises, I have also sporadically worked freelance for over eight years building couture pieces of the internet for various private clients and businesses, and am currently working as a technician, where I do get to occasionally revel in the internal or external sites, having fixed everyones printers.

As such, I am proficient in most common server and client-side technologies, including the latest and greatest that HTML and CSS has to offer (arrows were always easy). If you want to see examples of my code, you should check out some of the GitHub repositories I've contributed too.

Server Side

  • Ubuntu
  • Nginx
  • MySQL 5


  • CentOS
  • Apache
  • PHP 5

Client Side

  • HTML 5
  • JavaScript
  • WordPress 3


  • CSS 3
  • JQuery


Having taken over control of eustasy, a collaborative resources and learning organisation for both budding and more experienced web developers and designers, I quickly founded How to Ubuntu, which I continue to write tutorials and other articles for. More recently I have started how to elementary os as an alternative to How to Ubuntu for this new, exciting, and, above all, beautiful operating system.


Coffee Beans don't exist,
and Orange does have a Rhyme.

Coffee Beans and other Lies is the ground-breaking new exposé from Lewis Goddard, brutally debunking everything from common misconceptions, to downright porkies.

With over 100 hundred Myths, Lies, Legends and Misconceptions, this book is surely a must have for any self-respecting human being.

Coffee Beans and other Lies is not limited by mundane things, such as references, or, indeed, taste. In fact, the entire book is basically a list of things you've been ignorant about for the preceding portion of our life.

Coming Soon to


Gaming is one of the greatest team-building exercises going, since it's one of the few team-building exercises people volunteer for, and not just to get out of doing work! I can usually be found playing strategy games on Steam.

Communication & Team Organisation

Back when Moon Breakers was a flourishing community, I organised a team of twelve players, counting classes and making sure all bomber runs and raids had a suitable size fighter escort to complete their missions. We ranked 3rd out of more than a dozen teams for several weeks before development of the game was cancelled when the owners ran out of money.

Navigation & Orientation

Knowing where you stand is good. Knowing where you want go and which direction is better. Leading a team, who are, of course, trying to get lost, can be difficult of times, but keeping good bearings over time, using landmarks as points, and breaking everything down into manageable chunks helps keep everyone on the same page, even if they're not quite together.

Resource Management

Controlling time and money is often at the forefront of a project, and so it is in games. When not limited by physics, you are limited by space, line of sight, ammunition, or whatever other resources are at your disposal. Focusing on obtaining that which you need and spending only what you can spare is often the difference between winning a match and defeat.

Threat Awareness

Tracking every threat to a team or project is paramount in a world filled with enemies, something amplified in a game environment. A player with no cover and no team watching their back is an easy target for anyone with even basic stealth capabilities, so you must protect your assets, from whichever threat poses the highest risk if ignored or simply unobserved.


The quickest way to contact me quickly is probably Twitter, although Google+ is nice for nerdier stuff. If you don't want to contact me on Twitter or Google+, then you can send me an email.

Issues or Questions about any of the GitHub repositories I contribute to should be posted there, that way the issues can be used for reference and I can get a warm, fuzzy feeling when I close them.