April 21, 2026
Wine + wisdom = flame war
Drunk Post: Things I've Learned as a Senior Engineer
Drunk dev’s late-night “truths” spark a code cult war, job-market reality check, and money-talk pileup
TLDR: A viral “drunk wisdom” post from a veteran engineer sparked fights over dynamic languages, jokes about cult-like work methods, and a reality check on today’s tougher job market. The thread swerved from code philosophy to money tips, revealing what devs really worry about: careers, interviews, and retirement readiness.
A boozy brains-dump from a 10‑year data engineer resurfaced on r/ExperiencedDevs, and the comments lit up like a deploy gone wrong. The post is all “change jobs to level up,” “tools don’t matter… actually they do,” “dynamic languages forever,” and wild love for interns. The crowd? Half nodding, half rage‑typing, fully entertained.
The loudest crossfire: dynamic vs. static. One reader barked “don’t build serious stuff in dynamic languages,” while others clapped for the author’s “fight me” energy. “New job in two weeks” became a punchline—users say that was boom‑era bravado, not today’s market. Meanwhile, the author’s swipe at interview trivia got backup, with one commenter comparing coding quizzes to pharmacists cramming chemistry just to ring up pills—industry shade, maximum strength.
Then the thread took a left turn into cult memes: folks laughed at “TDD is a cult” (TDD = test‑driven development) and admitted some Agile/Scrum workplaces feel like rituals with standups instead of candles. The nerdiest record scratch? “LISP is the greatest” had people bailing mid‑drink. And just when it was all code wars, a veteran swooped in with personal finance PSAs: max your 401(k) (US retirement plan), grab an HSA (health savings account), touch your budget before you touch another framework. In short: messy, real, and way too relatable—just like a late‑night group chat after one glass too many.
Key Points
- •The article preserves a candid list of lessons from a data engineer with 10 years’ experience, originally posted while intoxicated.
- •Career advice includes advancing by changing companies, leaving roles when unsatisfied, and being honest (but measured) with managers.
- •Operational stance: more than one on-call wake-up per quarter indicates systemic issues that should be fixed or warrant quitting.
- •Technical priorities emphasize understanding core engineering patterns over specific stacks, writing clear documentation and proposals, and maximizing code readability (or avoiding code when possible).
- •Language views: appreciates dynamic languages; contrasts Python and C++ roles; recommends Java for general utility; calls Lisp the greatest; asserts SQL is highly lucrative for beginners; praises interns and says full-stack web developers are underpaid.