CLI
Post #4537, on Jun 23, 2022 in TG
When dad discovers you still reach for the mouse while coding
Description
Black-and-white two-panel meme using the classic father-and-grown-son format. Top panel shows the father leaning over a railing telling his son, “One day you’ll be a man.” The son, wearing a plaid shirt, replies, “Dad, I’m 32.” Bottom panel zooms in on the father’s face as he delivers the punchline: “But your development workflow requires a mouse.” The humor riffs on seasoned developers who pride themselves on pure keyboard-driven tooling (Vim, tmux, CLI) and view any reliance on a mouse inside an IDE as amateurish. It pokes fun at editor wars, terminal elitism, and the cultural clash between GUI-heavy IDE users and command-line power users
Use J and K for navigation
Comments
6Comment deleted
We didn’t spend two sprints parallelising the CI pipeline just so you could burn the savings dragging your cursor to the Run button
The same engineer who judges you for using a mouse just spent three hours debugging a vim macro that could've been a simple find-and-replace in VSCode
At 32, you've survived multiple JavaScript framework rewrites, navigated the microservices-to-monolith-back-to-microservices cycle, and can recite the CAP theorem in your sleep - but if you're still reaching for that mouse to copy-paste in your terminal instead of using tmux with vim keybindings, are you really ready for that Staff Engineer title? Real engineering maturity isn't measured in years of experience; it's measured in how many consecutive hours you can code without your hand leaving the home row
Senior dev milestone: when your whole toolchain works over a flaky SSH session at 2 a.m. - if it needs a mouse, it’s a demo, not an incident
Senior devs don't need mice - they resize splits with C-w and SSH into prod outages like true adults
If your “workflow” needs a mouse, it’s not a workflow - it’s an unversioned, nondeterministic clickstream with no replay