A/B Testing vs. Feature Flags: They're Not the Same Tool
Feature flags and A/B tests share infrastructure but answer different questions. A guide to telling them apart before your rollout data lies to you.
Read article →Insights on feature flags, progressive rollouts, and modern engineering practices from the ShipSilently team.
Feature flags and A/B tests share infrastructure but answer different questions. A guide to telling them apart before your rollout data lies to you.
Read article →Your flag configuration is production config that lives in exactly one place, on someone else's servers, with no backup. Here's a script that fixes that for LaunchDarkly in about four minutes, and what the export quietly leaves behind.
Read article →A copy-paste prompt library for shipping real features with an AI coding agent, dark mode, search, notifications, onboarding, and more, plus the one habit that keeps a fast-moving feature from taking down production.
Read article →On July 10, LaunchDarkly's SDKs started 'giving up permanently' and the official remediation was to restart every affected application and Relay Proxy. That's not a recovery strategy, it's a design decision. Here's the design that makes restarts unnecessary, and how we built it.
Read article →A build guide for adding a command palette to your product: the data model for commands, fuzzy search, keyboard navigation, accessibility, and shipping it to power users first.
Read article →A practical guide to adding dark mode: semantic color tokens, respecting OS preferences, avoiding the flash of wrong theme, and rolling it out to real users without a big-bang launch.
Read article →A practical guide to adding file uploads: presigned URLs, validation, virus and content-type checks, progress and resumability, and rolling the feature out without opening a security hole.
Read article →A build guide for adding a referral program to your product: the data model, fraud-resistant attribution, reward mechanics, and how to test whether it moves the needle before rolling it out to everyone.
Read article →A guide to adding magic-link and passwordless authentication: token design, expiry and single-use, rate limiting, the security tradeoffs, and migrating existing users without locking anyone out.
Read article →A pragmatic guide to shipping your first AI feature, scoping it, controlling cost and latency, handling the ways LLMs fail, and rolling it out so a bad response never becomes a bad quarter.
Read article →A design and engineering guide to adding undo: the deferred-delete pattern that beats confirmation dialogs, soft deletes, undo stacks, and shipping it so users trust your product more.
Read article →A complete guide to building an in-app notification system: the schema, unread counts that stay accurate, real-time delivery, user preferences, and how to launch it gradually instead of pinging everyone at once.
Read article →A field guide to telling feature flags, config values, and user settings apart, three things that look identical at the API boundary and behave nothing alike. Miscategorize them and you end up with 240 'flags', a dashboard nobody trusts, and a 3am page about a setting that should have been a database row.
Read article →deathbyclawd.com isn't wrong, Claude really can one-shot a feature flag service in an afternoon. The problem isn't the first afternoon. It's the next two hundred. A friendly, no-insults case for paying us a small amount of money instead.
Read article →On the web, a flag flip reaches every user in seconds. On mobile, your rollout has to survive review queues, offline devices, persistent on-disk state, and the user who hasn't updated since 2024. A different problem, a different set of patterns.
Read article →Standard percentage rollouts don't translate cleanly to LLM features. Sticky bucketing, shadow evaluation, and capability gating are the three patterns AI engineers actually need, and why your latency, cost, and eval signals all behave differently.
Read article →Progressive rollouts let you ship slowly. Kill switches let you stop instantly. A practical guide to the on-call engineer's most underrated tool, and how to design your code so it actually works at 3am.
Read article →From cowboy push-to-prod to a real flag system, a brutally honest map of how engineering teams actually evolve their release strategy, and how to know which level you should be at.
Read article →Feature flags split deployment from release. Here is what that buys a team that ships daily, and where the practice starts to cost you.
Read article →How evaluating feature flags at the edge eliminates latency and transforms the performance profile of your application.
Read article →How to adopt trunk-based development using feature flags to keep your main branch always deployable while shipping large features incrementally.
Read article →How to stage a rollout with feature flags, from a 1% canary through percentage releases, and what to watch at each step.
Read article →Feature flags improve velocity, but left unchecked they become a source of complexity. Learn how to keep your flag inventory clean and maintainable.
Read article →