Pushing the whole company into the past on purpose
rachelbythebay.com
Pushing the whole company into the past on purpose
1–10 of 139 posts
Re: Pushing the whole company into the past on purpose
#2This seems to be the reason for writing about the topic right now:
> So, yes, in June 2015, I slowed down the whole company [Facebook] by a second.
> Of course, here it is ten years later, and the guy in charge just sent it back fifty years [by ending fact checking?]. Way to upstage me, dude.
Re: Pushing the whole company into the past on purpose
#3This seems to be the reason for writing about the topic right now: > So, yes, in June 2015, I slowed down the whole company [Facebook] by a second. > Of course, here it is ten years later, and the guy in charge just sent it back fifty years [by ending fact checking?]. Way to upstage me, dude.
Facebook maybe? She mentions the cat factory
Re: Pushing the whole company into the past on purpose
#4Nice descriptive article. I've done this on purpose too to debug
remote filesystem syncs and cryptography problems where machines are
out of sync. My GPS wall clock is handy for adjusting NTP, but the
time it takes to scan my eyes from the wall back to the monitor.. you
really do need two stacked like she did. So I now figured to use
transparrent terminals each logged into a different host and lay them
over one another running "watch -n1 date".
Would have been nice to have some more network, code and command line examples. You need to set up a local ntpd and need to point your local master at that temporarily. A better utility to write would be "timediff -s1 -s2" that takes two time servers and shows the offset. I bet there's a way to do that in one line. Anyone?
Re: Pushing the whole company into the past on purpose
#5I’m not sure I get the fifty years bit at the very end. Anyone care to explain?
Re: Pushing the whole company into the past on purpose
#6I’m not sure I get the fifty years bit at the very end. Anyone care to explain?
I believe the author worked at Facebook in the past. The "fifty years" bit is likely a reference to that company's recent policy change that explicitly re-authorizes the use of what are rightly considered slurs - even if they were common sentiment to express publicly fifty-some years ago.
Re: Pushing the whole company into the past on purpose
#7I’m not sure I get the fifty years bit at the very end. Anyone care to explain?
I believe the author worked at Facebook in the past. The "fifty years" bit is likely a reference to that company's recent policy change that explicitly re-authorizes the use of what are rightly considered slurs - even if they were common sentiment to express publicly fifty-some years ago.
Aye, that makes sense (not the slurs, but the explanation). Thanks.
Re: Pushing the whole company into the past on purpose
#8"Reenact the past , be the past, past becomes glorious present" Isil
Re: Pushing the whole company into the past on purpose
#9> Of course, here it is ten years later, and the guy in charge just sent it back fifty years. Way to upstage me, dude.
I feel like there's a link to a story missing there
Re: Pushing the whole company into the past on purpose
#10This seems to be the reason for writing about the topic right now: > So, yes, in June 2015, I slowed down the whole company [Facebook] by a second. > Of course, here it is ten years later, and the guy in charge just sent it back fifty years [by ending fact checking?]. Way to upstage me, dude.
The fact checking is the tip of the iceberg — it's what the marketing machine led with because it's the least objectionable. Far far worse is letting queer people like myself be called mentally ill, though not any other group (e.g. religious people). Yes, it's part of the common discourse, but the common discourse is objectively morally abhorrent.
I worked at FB for a decade, and I now am rooting for its complete destruction.