zlacker

>>topshe+(OP)
Is adding a feature-flag really the same as pushing the feature into the browser immediately? It can easily just be part of a SWE needing the flag in place in order to continue work without impacting anything else, even if that thing never ever launches.

In general Google engineers don't tend to work on branches, especially long-running ones. Incremental small code reviews are the expectation. The general process would be to stick things securely behind flags and continue development without turning it on, even if it never ever launches.

Not saying this work should be done -- it shouldn't -- but code being pushed is not the same as "we're going to make this happen tomorrow, no matter what."

>>cmrdpo+04
Companies don't usually make a habit of having their employees work on something they don't intend to pursue.

>>duerra+P4
Yes, they actually do. Or rather, there is no "company", there are thousands of different decision makers.

My point is that at some other company (e.g. Apple) it would be done in secret on a branch somewhere, then big-bang merged later.

Google's process doesn't tend to work that way.