-
·
Let’s Encrypt And The Moment HTTPS Became Easier To Justify
A 2016 reflection on why free, automated TLS certificates changed the practical conversation around HTTPS for ordinary business websites.
-
·
CSS Custom Properties And The Problem With Repeating Yourself
A practical look at why CSS custom properties felt useful once front-end projects started carrying repeated colours, spacing values and interface states across larger websites.
-
·
PHP 7 And Why Old Server Assumptions Needed Revisiting
A practical reflection on PHP 7 in 2015, and why faster server-side performance meant developers needed to revisit old assumptions around hosting and legacy code.
-
·
Let’s Encrypt And Making HTTPS A Normal Website Decision
A practical article about Let’s Encrypt in 2015 and why easier certificates changed how small websites could approach HTTPS.
-
·
Babel 6 And The Cost Of Writing Future JavaScript Today
A practical reflection on Babel 6, ES2015 and the point where writing modern JavaScript meant accepting a clearer build process.
-
·
AMP And The Mobile Web Performance Problem Becoming Harder To Ignore
A practical 2015 article about AMP and why the announcement reflected a wider frustration with slow, heavy mobile pages.
-
·
Node.js 4 And Rebuilding Trust Around Server-Side JavaScript
A practical article about Node.js 4, the io.js reunification and why stability mattered as much as features for server-side JavaScript in 2015.
-
·
Bootstrap 4 Alpha And Rebuilding A Shared Front-End Base
A 2015 reflection on Bootstrap 4 alpha and why the more interesting discussion was the need to rebuild shared front-end systems once real projects had exposed their limits.
-
·
jQuery 3 Alpha And The Question Of How Long To Carry Old Browsers
A practical look at the jQuery 3 alpha release in 2015 and the wider question of when a project should stop carrying older browser behaviour by default.
-
·
ECMAScript 2015 And Writing JavaScript With A Longer View
A practical 2015 article about ES2015, and why the new JavaScript features mattered most when they made larger codebases easier to understand over time.