March 19, 2026
Buzzwords, meet the shredder
Translate Garry Tan's LinkedIn-speak to plain English
Garry Tan README gets de-buzzworded; commenters launch a 'no more LinkedIn-speak' revolt
TLDR: A developer used Kagi to translate Garry Tan’s gstack README from LinkedIn buzzwords into plain English and opened a PR. Commenters cheered the clarity, roasted corporate-speak, and debated the snark—proof that cleaner docs help real users, especially non-native readers, and that jargon fatigue is very real.
The internet finally found a common enemy: LinkedIn-speak. Developer tornikeo took a red pen to Garry Tan’s “gstack” README, ran it through Kagi’s LinkedIn-to-English tool, and opened a pull request. Cue the crowd going wild. One commenter joked this PR might be the repo’s peak achievement, while another simply stamped it “LGTM” (translation: looks good to me). There’s even a link to the tool for the curious: Kagi translator.
The vibe? A full-on buzzword detox. “Genius move,” said one fan, blasting “AI-adjacent writing” and people “with a stick up their ass” acting like Aristotle. Others cheered the bluntness: “Crass, but you gotta fight fire with fire.” A license purist waved the MIT flag—meaning the project is free to remix—calling this translation a perfect use of that freedom. A non-native English speaker thanked the author for cutting the fluff so they could actually understand it. Meanwhile, someone pitched a startup idea: a “Snyk for LinkedIn-speak” to sniff out jargon at scale. Final chorus: “Ship it.”
So yes, this is a tiny PR—but the comments made it a referendum on corporate gobbledygook. The crowd wants plain English, fewer grandstanding gurus, and docs that help builders get to work. The roast is loud, the message is clear, and everyone’s hitting “approve” with a smirk.
Key Points
- •A PR proposes translating the gstack README from “LinkedIn-speak” to plain English.
- •The author used Kagi’s LinkedIn-speak translator to produce the rewrite.
- •The PR is open with one commit and targets garrytan:main from tornikeo:patch-1.
- •At least one reviewer (Frizlab) approved the changes; additional comments indicate support.
- •Conversation references the repository’s MIT license and clearer documentation as benefits.