Strategies you can implement to stand out in a crowded job search process.

Users shouldn't see stack traces. Devs shouldn't see JSON parsing errors. Send the right error to the right place.

Several software delivery principles are widely applicable, beyond the strict definition of "software".

If you practice TBD with days-long branches, is it still TBD? I don't know. But it's certainly not continuous integration.

There are two related practices that are often called "Trunk-Based Development", which can lead to some confusion.

If your project doesn't already use a static analysis tool to detect obvious bugs, start today!

Multi-stage software delivery means no hotfixes, or lots of extra work.

CloudFlare pages, Vercel, Next.js and other next-gen CI/CD tools.

You don't need a dashboard until the difference you're trying to measure is too small to be casually obvious.

With respect to Goodhart's law, the DORA metrics are a place to start.

My opinion is that days are usually better than story points, for the simple reason that they're less confusing.