CLI
Post #4849 · source on Telegram
When your regex fails and you’re left SED instead of satisfied
Description
A three-panel “bad pun husky” meme shows a grey-and-white husky on a bed holding a plush toy. Panel 1: the dog looks sideways while white block-cap text overlaid reads, “HOW DOES AN IT GUY FEEL AFTER FAILING TO DO REGEX?” Panel 2: the husky turns toward the camera, mouth slightly open, with the single word “SED” in bold white capitals centred across the frame. Panel 3: the husky grins widely with teeth showing, clearly pleased with its own joke. The gag is a Unix command-line pun: ‘sed’ is a classic stream-editing tool that uses regular expressions, while the homophone “sad” conveys the emotion of failing at regex. Developers familiar with shell tooling, regex frustration, and groan-worthy puns will recognise the CLI humour immediately
More like this
More like this in CLI →
Use J and K for navigation
Comments
11Comment deleted
Running sed -i in a one-liner on prod is that senior rite of passage where you discover both your regex and your rollback strategy were non-greedy
The real tragedy is when you finally get your sed regex working perfectly, only to realize you forgot the -i flag and all your changes went to stdout instead of the file - now THAT'S when the existential 'sed'ness truly hits
After spending three hours debugging a catastrophic regex that somehow matched everything except what you needed, discovering sed's simple 's/problem/solution/' syntax feels less like settling and more like finally understanding why the Unix philosophy exists - sometimes the tool that does one thing well beats the Swiss Army chainsaw every time
Regex “didn’t work,” so someone reached for sed -i - congrats, you just shipped a write-only DSL to prod
Regex lookahead hell in code: 3 hours of despair. Sed one-liner: instant victory. CLI elders know the real regex power lies in streams, not libraries
Regex failed? Classic - next step is `sed -i` against live configs, because nothing calms catastrophic backtracking like irreversible text surgery in production
that happens too regular Comment deleted
-i "s/know/knew/g" Comment deleted
didnt get it, explain plz Comment deleted
https://www.gnu.org/software/sed/manual/sed.html Comment deleted
Ahh, sed. Helped me a lot Comment deleted