It's my job and still a passion; articles, tutorials, notes, and resources exploring web development are all contained here.
I've been a full-time web developer since 2004, and a keen hobbyist before that. I've been a member of the HTML Working Group and Responsive Images Community Group. If you've heard of me before it's likely because you've also heard of Adaptive Images; an old but still useful project of mine.
I've been writing about web related topics for a decade, and though these things date quickly my archive of old posts is still available, because link-rot is bad.
What I write
I write under the following categories:
Articles are long-form discourse about whatever topic they address. They've usually had considerable thought put into them, and are sometimes an expansion on a topic raised earlier as a 'notes' post.
Off-the-cuff thoughts, notes, and items of interest; these have less time dedicated to them than Articles and sometimes will lead to Articles later on.
Tutorials are intended as step-by-step instructions to achieve a specific task; they're focussed on that and not so much about any broader related topics.
Things I've seen elsewhere that I'd like to refer to in the future; essentially these are 'bookmarks' for myself, which I thought might be good to share.
N.b., Timeline excludes Resource posts:
Using VueJS to replace existing functional HTML with an enhanced Vue component, only when JS is available... is a lot easier than I realised.
A paradigm shift in Web Development is underway, as exciting as it is intimidating. For traditional web developers who played it safe over the last few years, the time to re-assess the landscape has long since arrived...
There's a non-zero cost to implementing new CSS features, and you need to decide when you can pay it.
The biggest trend and problem of the last few years is ever bigger web pages wasting ever more bandwidth. And we're given tools to load more crap based on a guess as to what the user might want to do next?
My trick for creating 'read more' links that work well for everyone.
The why, when, and how of using nginx to cache a CMS's output.
HTTP2 will mean a change in how we should build websites. The best practices of HTTP1 are harmful in a HTTP2 world.
I've never built a website based on a third-party framework, but I recently had cause to try one, spending a week with Foundation. Here's what I found...
A quick tip on how to fix things if your asset uploads in Craft seem to just hang.
How I used nginx and Craft to rebuild this website.
It's taken almost three years to finally get around to, but at long last this website is sporting a design and running on a CMS I actually like.
When the Great Firewall of China starts hosing your server with unexpected and unrelated traffic, how do you deal with it?
Why is it still so hard to set up a portable development environment?
We have some new technologies coming up which are going to have a big impact on what we do and how we do it.
My strategy to ensure HTML's new responsive image attributes don't grow out of control when you use them.
Most security questions are at best obstructive, at worst terribly insecure.
Organising SCSS for better readability and faster coding.
I've been playing with Craft for a short time, like they promised on their website – I love it. Maybe you should try it.
Why I don't trust applications that laregly subsist on their plugins.
With new features like Web Components and Element Queries, what will the mark-up of the future look like?