npm Dependency Hell
A deep dive into the terrifying moment when you run npm install and 1,347 packages appear in your node_modules, three of which are maintained by a single person in Nebraska.
// A literary, self-ironic dev blog|
A deep dive into the terrifying moment when you run npm install and 1,347 packages appear in your node_modules, three of which are maintained by a single person in Nebraska.
It finally arrived -- the long-awaited and controversial purchase. I really wanted it, but the price and reviews about its balance kept me from pulling the trigger. A bit of spontaneity and here it is.
Spring is coming and I'm getting restless. An idea was born: build a multiplayer top-down shooter in the browser with JavaScript, set in space. Working title: STDS (Space Top Down Shooter).
It's 4 AM, insomnia got me again. Usually I go work. For me this is a blessed time of peace and quiet -- what more do you need to write beautiful, maintainable code?
A chronicle of the five stages of grief as experienced through a CI/CD pipeline that refuses to turn green, and the lessons learned along the way.
How I went from 'types are for people who can't hold code in their head' to 'I will never write untyped JavaScript again' in about six months.
Every developer inherits a codebase they didn't write. The question isn't whether to refactor -- it's how to do it without losing your mind or breaking everything.
A love letter to git bisect -- the underappreciated tool that turns a haystack of commits into a binary search for the needle that broke everything.
In which a simple color change spirals into a deep dive through cascading stylesheets, specificity calculators, and the liberal use of !important.
There's a special kind of clarity that comes at 3 AM when it's just you, a bug, and the quiet hum of a monitor. Or maybe that's just sleep deprivation talking.