When the code review asks if you shipped anything yesterday
Description
Two-panel anime meme of a katana being unsheathed. Panel 1 shows both hands gripping a still-sheathed sword; only a sliver of steel is visible and the blade is over-laid with the single word “YES” in bold white capitals. Panel 2 shows the sword fully drawn; the entire blade now displays the longer caption “YESTERDAY I WAS IN MEETINGS ALL DAY.” The scene uses crisp cel-shaded colors, bright blue sky background, purple-wrapped hilt, and exaggerated hand proportions typical of modern shōnen animation. Technically, the joke mirrors the maker-vs-manager schedule clash: engineers asked for output brandish a terse affirmative, but once the whole story is ‘drawn,’ it’s clear continuous meetings left zero time for actual commits - an experience painfully familiar to senior devs juggling sprint ceremonies, stakeholder syncs, and quarterly OKR reviews
Comments
6Comment deleted
My git diff was empty, but Jira gained 42 comment threads - turns out throughput moved from CI pipeline to calendar pipeline
The best part about being a senior engineer is having the authority to decline meetings, but also the responsibility to attend all of them
When your standup answer evolves from 'blocked' to a detailed retrospective of every Zoom call that prevented you from actually writing code - because apparently 'in meetings' is the enterprise equivalent of 'compiling' as the universal productivity black hole explanation
Yesterday’s DORA looked great - mean time to meeting near zero, deploy frequency zero; turns out the calendar is our monolith
Asked for a binary yes/no, my maker-schedule type widened it to a string: 'Yes - terday I was in meetings all day.'
Yesterday: 8 hours of 'let's align' yielding zero PRs. Today: Unsheathed, merging at lightspeed