3 ms·
For those confused, this is basically a fan-fic in reference to this piece [0] from McSweeney's 0: https://www.mcsweeneys.net/articles/faq-the-snake-fight-port
by pimlottc 3y ago
For those confused, this is basically a fan-fic in reference to this piece [0] from McSweeney's
0: https://www.mcsweeneys.net/articles/faq-the-snake-fight-portion-of-your-thesis-defense https://www.mcsweeneys.net/articles/faq-the-snake-fight-port...
- tialaramex 3y agoI was like "Wasn't that years ago?" - a friend of a friend did her PhD on stuff related to AO3.
- riffraff 3y agoI'm glad I read the fanfic first and the original later. They are both wonderful but the complete confusion caused by reading the email thread with zero context was an added joy, while the FAQ were hilarious anyway.
- axus 3y agoI liked this one, which included an offhand reference to SMB share incompatibility: https://www.mcsweeneys.net/articles/my-comments-are-in-the-google-doc-linked-in-the-dropbox-i-sent-in-the-slack https://www.mcsweeneys.net/articles/my-comments-are-in-the-g...
- vundercind 3y agoSweet shit. That rings true. We have so many tools at work with significantly-overlapping functionality, but use like a different 10% of each one’s features. My god, just pick a few and consolidate. The lost productivity is enormous. Multiple tools with issue trackers. Multiple tools with secrets management. Multiple tools with ci pipelines. Multiple code repo hosts. Multiple project management systems. Multiple container and package registries. Multiple code vuln scanners. Messaging systems. Logging & alerting systems. Documentation hosts. FFS a few of our tools do all of those. But that’s like seven or eight different tools, as we use them. The process of getting anything to work, or finding any given piece of info, often looks like your linked piece.