> At some point, I realized that if I wrote a wiki page and documented the things that we were willing to support, I could wait about six months and then it would be like it had always been there. Enough people went through the revolving doors of that place such that six months' worth of employee turnover was sufficient to make it look like a whole other company. All I had to do was write it, wait a bit, then start citing it when needed.
> I used to be on a team that was responsible for the care and feeding of a great many Linux boxes which together constituted the "web tier" for a giant social network. You know, the one with all of the cat pictures... and later the whole genocide thing and enabling fascism. Yeah, them.
I love how people are so willing to criticise companies that paid their salary but not their willingness to ignore the issues in the name of the fat paycheque.
This is clearly a reference to Meta, and in that sense the writing has been on the wall for years.
I wonder if the author feels or takes any responsibility in directly enabling that genocide and that fascism with their direct work.
"That's supported" has no universal interpretation beyond physically describing a tabletop atop legs.
Absent a clear/consistent definition, people interpret "support" in the most favorable way possible from the seats in which they sit. Then, all around sadness ensues.
> 1. Assemble a small council of trusted senior engineers
> 2. Task them with creating a recommended list of default components for developers to use when building out new services. This will be your Golden Path, the path of convergence (and the path of least resistance).
> 3. Tell all your engineers that going forward, the Golden Path will be fully supported by the org. Upgrades, patches, security fixes; backups, monitoring, build pipeline; deploy tooling, artifact versioning, development environment, even tier 1 on call support. Pave the path with gold. Nobody HAS to use these components … but if they don’t, they’re on their own. They will have to support it themselves.
Reading this I'm mostly shocked that groups had the power to throw boxes onto their outward-facing infrastructure and she had to handle that reactively. Like, it's not "requisition a public network server" but rather "you just jam it out there and we'll either baby it or boot it". That's crazy loose for a major corp.
13 comments
[ 2.0 ms ] story [ 29.5 ms ] threadLike!
This really doesn't narrow it down.
> and later the whole genocide thing and enabling fascism.
Still not helping.
https://news.ycombinator.com/item?id=13400687
https://medium.com/wogrammer/rachel-kroll-7944eeb8c692
https://www.usenix.org/conference/srecon16/speaker-or-organi...
I love how people are so willing to criticise companies that paid their salary but not their willingness to ignore the issues in the name of the fat paycheque.
This is clearly a reference to Meta, and in that sense the writing has been on the wall for years.
I wonder if the author feels or takes any responsibility in directly enabling that genocide and that fascism with their direct work.
But hey, a fat paycheque is a fat paycheque.
"That's supported" has no universal interpretation beyond physically describing a tabletop atop legs.
Absent a clear/consistent definition, people interpret "support" in the most favorable way possible from the seats in which they sit. Then, all around sadness ensues.
> 1. Assemble a small council of trusted senior engineers
> 2. Task them with creating a recommended list of default components for developers to use when building out new services. This will be your Golden Path, the path of convergence (and the path of least resistance).
> 3. Tell all your engineers that going forward, the Golden Path will be fully supported by the org. Upgrades, patches, security fixes; backups, monitoring, build pipeline; deploy tooling, artifact versioning, development environment, even tier 1 on call support. Pave the path with gold. Nobody HAS to use these components … but if they don’t, they’re on their own. They will have to support it themselves.