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.
I have two bad traits:
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 properties, 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, but only after fixing everyones printers.
I am proficient in most common server and client-side technologies, including the latest and greatest that HTML and CSS has to offer. If you want to see examples of my code, you should check out some of the GitHub repositories I've contributed too.
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 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.
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.