I recently wrote this piece for the Evoluted blog to debunk the false perception that quick fixes can be done in 5 minutes. As developers, we often underestimate our own processes and devalue the work we do. I wanted to highlight the many stages of the development process for bug fixes. Sometimes, we need to step back and look at the bigger picture.
Ten years ago I started working full-time as a web developer, leaving behind my career in Physics. It is a decision I have never regretted. For the last decade I have been able to spend my days working on what, for a long time, was mostly a hobby. My passion for developing websites continues today.
Ire Aderinokun explains how you can set a performance budget for your website and check that it is conforming to it using Lighthouse. As she points out, Lighthouse can be run from the command line which means we can incorporate the audit into our continuous integration process.
This is a great idea and definitely something I want to develop into my own workflow going forward.
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.