← Back to context

Comment by flippingheck

4 days ago

At $FAANG, ~all changes go through feature flags.

There are processes to make changes outside of feature flags, but they have enough friction that it's easier to just use a feature flag.

This level of paranoia is consistent with the blast radius of changes breaking Claude users.

I'd love to hear more about this. Though I usually write bespoke software for specific clients, I'm about to release my first general-availability application. It's a rust application with Python GUI on the desktop (Linux, Mac, Windows) and a skinny Android application that wraps the rust on mobile. I'm going to be gating features starting probably next week. I'd love to hear tips and experience for implementing feature flags, for both the desktop and mobile space.

Thanks!

  • To the guy who asked but his comment is dead:

      > Are you gating by license or user, or just by percentage of installs?
    

    I'm gating by version. I want to dogfood features personally before releasing them to all my users.