I’m not going to extol the virtues of encrypting your site and enabling HTTP/2. The advantages should be pretty obvious by now. The real issue is that when you’ve got your site(s) and your clients’ site(s) encrypted, you’re left with local development versions of the sites which are now at odds with the live version. And it’s always best to mirror your dev and live environments as much as possible to avoid those last-minute deployment panics. Like when I deployed the all-new Clearleft site only to find I hadn’t updated the image links to HTTPS so none of them loaded. Queue a frantic 10 minutes of find and replace throughout the site templates while people were telling me the site was b0rked. Fun times.
Welcome back, dear Internet traveller. I hope you’re sitting comfortably, because we’re going to cover a lot of ground in this part.
A year or so ago, I came across this post by Keith Cirkel, How to Use npm as a Build Tool and it stuck with me. At the time I was transitioning to
grunt both personally and for Clearleft projects. We had a discussion about the feasability of going full NPM and decided that using
gulp was still the best for us. There are plenty of great reasons to use
gulp and we will continue to do so at Clearleft, but for my personal site I decided to experiment with pure
NPM. And in so doing, show how easy it can be, particularly for small sites, to set up some simple tasks.
Some time around the last Steam sale I knew I couldn’t keep buying games I never intend to play. Or, at least, do not have time for. If I cared about the game, I would have bought it sooner, really. Instead, all I could feel was the burden of games unfinished. The list of which was ever growing. So I decided to make a literal list of those unfinished games and try to beat them before moving on. Or at least make a good dent. And here is that list. My games of shame: