How confident are you about deploying to production on a Friday? Should it really be an issue if you have the right tests in place? Chris Coyier’s Make it hard to screw up driven development post is well worth a read if you want to make your code safer to deploy at the end of a working week.
This is an interesting look at how we use casing in our code. In his blog post Brendt argues that snake case is more readable than camel case. I particularly like this point that he makes:-
Readable code, reduces cognitive load. Less cognitive load means more memory space for humans to think about other things, things like writing business logic.
I’ve always preferred camel case over snake case, but I think that has been for purely aesthetic reasons over how easy they are to read.
A quick look at how to set multiple rulers in Sublime Text 3 to help keep code readable using differing line widths to indicate soft and hard line length limits.
Using CDNs is great for improving site performance and lowering bandwidth usage on your server. However, they can also open up a security hole in your site. Troy Hunt has written a great piece about how you can protect your embedded content with subresource integrity.
The SRI Hash Generator website is a great resource for getting started with using subresource integrity (SRI).
I’ve written a piece on my Test Payment Cards cheat sheet for Smashing Magazine explaining the motivations behind it. You can read Testing Credit-Card Numbers In E-Commerce Checkouts over on the Smashing Magazine website now.
As every good developer knows the performance of their code is important. When building websites we want them to be light and fast to give the end-user a fantastic experience. However, far too often developers prefer to take shortcuts to make their lives easier, even at the expense of the site’s performance.
console.log(), but there’s much more to the Console object. This article discusses 5 functions of the Console object that you may not have heard of, but you’ll want to start using from now.
The other week Harry Roberts wrote Vim for people who think things like Vim are weird and hard (a really good read if you haven’t read it yet) and so I thought I’d share my own Vi/Vim cheat sheet.
Another good post from Harry Roberts, this time it’s why you should consider using Vim as your text editor of choice.
The mere concept of Vim is alien enough for most people to just end up dismissing or ridiculing it, but—if we’re to be objective—the fact that, yes, people still use an editor that is over 20 years old (in turn based on a tool from the 70s), and those people number in the hundreds of thousands, perhaps they might be onto something.
Personally I tend to work with Sublime Text as my main text editor, but dip into Vi/Vim often. Once you’ve learnt a handful of commands it starts to quickly become a powerful tool and it is well worth investing some time getting familiar with.
I’ve recently discovered Jack Franklin’s gulp-load-plugins plugin for Gulp and it’s really neat. Rather than have to specify each plugin, gulp-load-plugins will search your packages.json file and automatically include them as plugins.pluginName(). It has become my new favourite Gulp plugin.