Developer Priorities: When 'No Tests?' Hits Harder Than Romance
Description
This meme uses a black-and-white anime/manga art style to depict a relatable developer dilemma. The image shows a couple in an intimate moment, with one character leaning in close to the other, who is seated at a computer. A speech bubble from the affectionate character says, 'baby can you touch me already'. The developer at the keyboard, however, is completely focused on their screen, replying with a speech bubble that reads, 'Hold on. Someone commented ,,no tests?" on my PR'. The humor lies in the stark contrast of priorities. For a developer, a comment on a Pull Request (PR) calling out a lack of tests is a serious professional matter that demands immediate attention. This meme perfectly captures the obsessive focus required in software engineering and the way that professional feedback, especially about code quality and testing, can overshadow everything else, including personal relationships. It's a funny, exaggerated take on the developer's commitment to their craft and the cultural importance of robust testing
Comments
7Comment deleted
The fastest way to kill the mood is a failing CI pipeline. The second fastest is a 'no tests?' comment on a Friday afternoon PR
My partner thinks I’m commitment-phobic, but after that one time I merged without tests and got a 3 a.m. Sev-1, I only make promises that pass CI
After 15 years in tech, I've learned that 'no tests?' comments have a stronger pull than gravity - they'll find you during dinner, vacation, and apparently even foreplay. The real test coverage we need is for our work-life boundaries
When your PR gets the dreaded 'no tests?' comment, suddenly that 95% code coverage requirement doesn't seem like bureaucratic overhead anymore - it's the difference between merging before standup and explaining to the team why you're refactoring half the codebase to make it testable. Every senior engineer has been there: caught between 'it works on my machine' confidence and the cold reality that untested code is just a ticking time bomb with your name on the git blame
Branch protections don't care about pheromones - add tests or enjoy another lonely rebase
Branch protection’s stricter than my dating life: no touching until “no tests?” is resolved and the behavior is idempotent
PR reviews: where 'touch me' instantly mutates to 'test me' under peer scrutiny - commitment issues, anyone?