Skip to content
DevMeme
2373 of 7590
VersionControl Post #2639 · source on Telegram

The 'Test in Production' Gambit on GitHub

Description

A screenshot of a GitHub conversation captures a moment of developer candor and humor. The image displays several comments on a dark-themed GitHub page. The central comment, from the repository owner 'gkoberger', reads, 'I have no clue how to test this locally anymore, so in the spirit of this commit...Fuck It! I just merged and we'll see what happens.' This is followed by a link for others to test the live version. The project in question is 'stacksort', a known joke project that 'sorts' code by searching Stack Overflow. The surrounding comments add to the lore, with one user welcoming the developer back and another asking if they 'got home yet', referencing a past event. This meme is highly relatable to experienced developers who have faced situations where local testing becomes unfeasible and have felt the temptation to merge and hope for the best, colloquially known as a 'YOLO merge' or testing in production

Comments

7
Anonymous ★ Top Pick Some engineers use a canary release. This developer prefers the 'phoenix release' strategy: burn it all down in production and see what rises from the ashes
  1. Anonymous ★ Top Pick

    Some engineers use a canary release. This developer prefers the 'phoenix release' strategy: burn it all down in production and see what rises from the ashes

  2. Anonymous

    Shu: write tests. Ha: mock dependencies. Ri: merge the 2-year-old branch straight to master and let Datadog page whoever still remembers the monolith

  3. Anonymous

    The beautiful thing about merging untested code directly to master is that it transforms every user into a QA engineer with production access and no ability to quit

  4. Anonymous

    When your local environment is so broken that production becomes your staging server - because nothing says 'battle-tested architecture' quite like using your users as QA. The 'Fuck It! I just merged' approach: a time-honored tradition where confidence inversely correlates with test coverage, and the only CI/CD pipeline is 'Commit and Pray.' At least he provided a URL for brave souls to test - that's practically enterprise-grade risk management in startup culture

  5. Anonymous

    When your local setup is irreproducible, the acceptance test is the SLO - merge to master and watch the error budget

  6. Anonymous

    “I can’t test locally anymore, so I merged” - otherwise known as a canary deploy with 100% traffic and observability provided by GitHub emoji

  7. Anonymous

    Senior dev special: Skip tests, merge to master, treat prod as the ultimate integration suite - revert velocity measures your true skill

Use J and K for navigation