6 ms·
Was this caused by changes rushed before a holiday code freeze? I know nothing about FB, but it's customary for companies to stop pushing new binaries in early-
by puzzle 8y ago
Was this caused by changes rushed before a holiday code freeze? I know nothing about FB, but it's customary for companies to stop pushing new binaries in early-mid December and to leave ad systems alone a week before Black Friday or so.
- mathattack 8y agoMuch more than a week!
- seanyesmunt 8y agoYep. When I was at Walmart the code freeze started in early November, with only critical bug fixes going in, then continued until the start of January.
- kenhwang 8y agoI work in adtech and we went into code freeze about 2 weeks ago because the holidays are crazy.
- xiphias2 8y agoAt another big company we had a code freeze as well, but we found a bug in a new feature that we released. We were not allowed to fix the bug, so we were reverting binaries of the data processing pipeline. The problem is that the data was already created and not backwards compatible, so we just created new problems... strict code freeze together with a huge feature push is always a nightmare.
- fma 8y agoMy big company has code freezes and no planned deploys around holidays... Bug fixes are allowed, just need deviations.
- Drakim 8y agoThat's why you should first have a feature freeze, and after a while go into a code freeze.
- xiphias2 8y agoIt took weeks for the bug to be surfaced. I was working with conversions, which is rare and noisy data. The problem is that most policies are not adjusted for the subteams.
- googlryas 8y agoDoes facebook follow this practice? I know at least some other FAANG companies do, but does this go against 'move fast and break things'?