November 28, 2025
Deadline Drama, Spaghetti Code
Good engineers write bad code at big companies
Deadlines, reorgs, and pay games turn pros into panic coders
TLDR: Big tech’s messy code is blamed on constant reorgs, short tenures, and decade-old systems touched by newcomers. Commenters battle over cause: some say deadlines are the real villain, others argue strong seniors can avoid bad code, while another camp claims companies knowingly trade quality for flexibility.
The internet is clutching pearls over a spicy claim: big companies pay top dollar, yet still ship messy code. Commenters say the real circus isn’t the code—it’s the deadlines and churn. One camp argues constant reorgs and short stays (thanks to stock packages that drop after four years) force newbies to tweak decade-old systems they barely know. Another crowd fires back: seniors can write clean code from day one—just more slowly and with lots of questions.
The hottest drama? Deadlines. As one user insists, even the “old hands” get compromised when bosses want it yesterday. Then comes a corporate dagger: a commenter says companies deliberately treat engineers as “fungible” (aka interchangeable), trading deep expertise and quality for the ability to throw bodies at the “problem of the month.” Translation: chaos is a feature, not a bug.
It’s not all doom—there’s meta too. One user links a past thread proving this debate resurfaces on schedule like a bad sequel. And for comic relief, someone drops a roast track here, turning spaghetti code into pop culture. The vibe: frustrated, funny, and very online. Big Tech’s secret sauce? A mix of speed, turnover, and pressure—served with a side of hot takes.
Key Points
- •Short average tenure and four-year vesting structures lead many engineers to leave, limiting long-term codebase familiarity.
- •Frequent reorgs and internal mobility place engineers on unfamiliar systems and languages, making many contributors relative beginners.
- •Long-lived services (often a decade old) rotate through many owners, increasing the likelihood of inexperienced changes.
- •Reliance on “old hands” is informal; these experts are often reassigned and are overloaded, reducing their ability to ensure quality.
- •Deadline pressures and high change volume create an environment where quick, imperfect fixes are favored over high-quality solutions.