Deploying code and releasing a feature are two different days

<p>Shipping code is <strong>stressful</strong>. You have a full test suite of end-to-end tests, linting and manual verification only for something to crash in production. </p>

<p>Shipping an application that I didn't have access to was giving me heartburn. So I decided to create a lightweight feature flag tool.</p> <h2> The Problem </h2> <p>The team

<p>Two weeks ago we shipped a release. A small one by our standards: a reworked lookup field, a smarter default for the date control, and a permission check moved one layer

<p>Deploying new features to production is inherently risky. No matter how thoroughly you've tested, production has a way of surfacing issues that staging environments don't. A

<p>Shipping quickly isn’t the hard part anymore. The hard part is recovering when something goes wrong.<br /> A lot of teams still release features the same way: deploy code and

<p><a class="article-body-image-wrapper"

<h2> The 2am Dashboard That Started Everything </h2> <p>It was 2:47am when I opened our feature flag dashboard and realized I had no idea what had changed. P99 latency on our