Skip to content
DevMeme
3411 of 7590
CodeQuality Post #3744 · source on Telegram

When lawmakers ship code straight to prod without tests or reviews

Description

Screenshot of a tweet from the verified account "Jameson Lopp (@lopp)" on a white Twitter interface. The tweet reads: "Lawmakers are crappy coders. They don't KISS. They don't write tests. They deploy directly to prod. They rarely peer review code. They don't garbage collect unused routines. They continue heaping complexity upon complexity until the system collapses under its own weight." A timestamp below shows “6:18 AM · Aug 3, 2021 · Twitter for Android.” Visually, the profile picture, blue check, handle, and multiline text follow the typical Twitter layout on a white background. Technically, the tweet satirically maps governmental legislative processes to poor software-engineering practices: ignoring the KISS principle, lacking automated tests, bypassing staging environments, skipping peer reviews, forgoing dead-code elimination, and allowing unbounded complexity - classic ingredients of technical debt and eventual system failure

Comments

10
Anonymous ★ Top Pick Legislation is the only repo where a one-line bug fix arrives as a 2,000-page “omnibus” PR, code review is every two years by QA named “voters,” and rollback requires a constitutional migration script
  1. Anonymous ★ Top Pick

    Legislation is the only repo where a one-line bug fix arrives as a 2,000-page “omnibus” PR, code review is every two years by QA named “voters,” and rollback requires a constitutional migration script

  2. Anonymous

    The only difference between lawmakers and that one cowboy developer we all know is that when the cowboy's untested code brings down production, at least we can roll back the deployment - with laws, we're stuck debugging in production for decades while the original authors have already left the company

  3. Anonymous

    This is essentially describing a codebase with a 20-year technical debt backlog, zero test coverage, and a deployment strategy of 'YOLO to prod.' The real kicker? Unlike software systems that can be refactored or rewritten, this particular 'legacy system' requires a constitutional amendment just to change a variable name, and the original architects left no documentation except some parchment from 1787

  4. Anonymous

    Policy-as-code would be nice, but right now governance runs trunk-based development with no staging, zero feature flags, and a rollback policy called “judicial review” whose P99 latency is measured in decades

  5. Anonymous

    Policy is the worst legacy monolith: shipped straight to prod, tests are lawsuits, riders are memory leaks, "sunset clauses" are feature flags nobody flips, and rollback requires an election

  6. Anonymous

    We refactor legacy spaghetti; lawmakers just pile on a 2,000-page omnibus bill until the whole repo crashes

  7. @ivan_kostrubin 4y

    I would laugh on that, really, if that wasn't terrible truth of our lives :(( We all affected by this shit

  8. @picolino 4y

    Lawmakers just goes brrrr

  9. @AidDeath 4y

    Sad but true

  10. @clockware 4y

    I think they do peer review. Like 2+ readings

Use J and K for navigation