Why some of the opinionated advice in React's official docs worries me — technical documentation isn't the place for it.

I love Angular, but single page apps, bad blogs and the 2.0 rewrite are why I probably won't be using it on my next project.

I write bad code because there's no other way to start — the trick is improving it before anyone else has to live with it.

A tongue-in-cheek survival guide for the coming apocalypse, in which I officially call dibs on being a blacksmith.

Using a technical test to show how simple, staged refactorings turn working-but-opaque Ruby into code that's easy to read and extend.

Settling into a new contract means changing old routines — spotting what to improve and adapting is what keeps contracting exciting.

On 'company fit' in interviews: the best team I worked in thrived because we weren't all the same, so talk about what you add, not how you conform.

Career progression for developers seems to offer two paths, both ending in management — and I'm honestly not sure where mine leads.

Feedback on an interview pairing challenge — reimplementing SecureRandom — that tested Ruby trivia more than it tested real coding skill.

A shared link to Steve Tooke's piece on how your tests want you to change your design.