• Bringing a better share experience to the web

    So something I have often talked about with designers is the challenge in getting users to share content on mobile. The reason for this is that if the user is in their browser looking at content they are unlikely to be logged into their favorite social network like Facebook or Twitter because they are probably using an app for that. The data supports this too with this article from earlier in the year ‘Does Anyone Use Social Sharing Buttons on Mobile?’.

  • Making stakeholders aware of the impact of website performance

    When I build a website I obsess over performance. I will rip out a JavaScript library from a project and replace it by another to save an extra 10KB. I do this because I understand the impact of performance. Both as a developer who has built a wide variety of sites and as a user who spent last weekend struggling to get one bar of signal at a campsite.

  • Migration to Jekyll

    So recently the site hasn’t been as reliable as I would have liked, this is due to issues with the server hosting the site and even after migrating to much bigger Digital Ocean droplet I still had issues with stability. I therefore made the decision to migrate the blog to use Jekyll hosted on GitHub.

  • Write your own CLI tool using Node.js

    I originally wrote about how to write a command line utility in Node.js back in 2013 when I was first learning how to do it myself. In the three years that have past the Node.js ecosystem has continued to grow so I thought it was about time to update my original post. If you want to see the original post it is still online over here.

  • What does Responsive Web Design mean in 2016?

    The term Responsive Web Design was first coined by Ethan Marcotte in 2010 (if you haven’t read the original post on A List Apart I recommend that you find the time too http://alistapart.com/article/responsive-web-design). Since then the browsers have done lots to improve our experience building responsive sites, implementing lots of new features. In this talk I talk about some of these new features that you can use today, in 2016.

  • Fetch API in the browser, it has happened

    The worst part about working on sites that use AJAX is having to use the XMLHttpRequest API, unfortunately this isn’t always easy as we are using it for things it wasn’t really made for. To get around this developers often use libraries like jQuery or MooTools which provide an abstraction however underlying these libraries is still the same XMLHttpRequest API.