4 ms·

Any code changes take a non-trivial amount of time. It sounds like the solution is to delete more of the cookies on logout, but there may be other Facebook ser

by mnutt 15y ago

Any code changes take a non-trivial amount of time. It sounds like the solution is to delete more of the cookies on logout, but there may be other Facebook services that use them and need to be transitioned away.

cbs 15y ago
>Any code changes take a non-trivial amount of time Thats a awfully cautions attitude and smells like a huge cop out for the well known fly-by-the-seat-of-your-pants commit to live strategy that facebook has.
- pork 15y ago
  Whatever you've read, Facebook likely has a non-trivial push strategy, just like everyone else. Nobody at their HQ is committing directly to the live site.
  - cpeterso 15y ago
    Facebook's Release Engineering blog says a code change can go from commit to live in less than 60 minutes. Admittedly, they don't say how often they deploy. https://www.facebook.com/note.php?note_id=59150988919 https://www.facebook.com/note.php?note_id=59150988919
    - lbrandy 15y ago
      Code changes are easy at facebook. Messing with domains/cookies/security/static-resources/etc is more than a code change.
- mnutt 15y ago
  I don't work there, but where I work we deploy 10-20 times a day and if somebody asked me to change the way we store data in cookies, it would probably take a bit of time to roll out. I'm only defending them because it annoys me when people who aren't familiar with the software internals tell me "this is a minor change, it should take you less than an hour".
  - 0x12 15y ago
    To be fair though, not doing something is a lot easier to implement than to add new functionality. As a minimal implementation they could err on the safe side and stop tracking everybody for a bit until they've corrected their error.
    - deleted 15y ago
      [deleted]
- pbhjpbhj 15y ago
  Well first you have to create the other company to spin off the tracking to ...
revorad 15y ago
Clearly, "Move fast and break things" doesn't apply when it benefits anyone other than the corporation.

by mnutt 15y ago

cbs 15y ago

>Any code changes take a non-trivial amount of time Thats a awfully cautions attitude and smells like a huge cop out for the well known fly-by-the-seat-of-your-pants commit to live strategy that facebook has.

pork 15y ago
Whatever you've read, Facebook likely has a non-trivial push strategy, just like everyone else. Nobody at their HQ is committing directly to the live site.
- cpeterso 15y ago
  Facebook's Release Engineering blog says a code change can go from commit to live in less than 60 minutes. Admittedly, they don't say how often they deploy. https://www.facebook.com/note.php?note_id=59150988919 https://www.facebook.com/note.php?note_id=59150988919
  - lbrandy 15y ago
    Code changes are easy at facebook. Messing with domains/cookies/security/static-resources/etc is more than a code change.
mnutt 15y ago
I don't work there, but where I work we deploy 10-20 times a day and if somebody asked me to change the way we store data in cookies, it would probably take a bit of time to roll out. I'm only defending them because it annoys me when people who aren't familiar with the software internals tell me "this is a minor change, it should take you less than an hour".
- 0x12 15y ago
  To be fair though, not doing something is a lot easier to implement than to add new functionality. As a minimal implementation they could err on the safe side and stop tracking everybody for a bit until they've corrected their error.
  - deleted 15y ago
    [deleted]
pbhjpbhj 15y ago
Well first you have to create the other company to spin off the tracking to ...

revorad 15y ago

Clearly, "Move fast and break things" doesn't apply when it benefits anyone other than the corporation.