Common sense Memes

Junior dev asks for style guidance. Senior dev smugly says "just use common sense." Junior dev politely asks for actual linter config. Senior dev proceeds to forcefully inject "common sense" directly into their brain, which apparently translates to "whatever the LLM and linter say." Because nothing screams "common sense" like blindly following ESLint's 47 warnings about semicolons while your production server is literally on fire. The real kicker? Everyone's "common sense" is wildly different. One person's common sense is 2-space indentation, another's is tabs, and a third person's involves sacrificing a rubber duck to the code gods before every commit. Just give them the .eslintrc file, Karen. It takes 30 seconds and saves everyone from the philosophical debate about whether trailing commas are a war crime or a gift from the heavens.

The tea bag is still wrapped in its paper, sitting in cold water with the string hanging outside the mug. Classic case of "it's so obvious, why would I document it?" syndrome that plagues software development. Future maintainers of this tea codebase will spend hours debugging why caffeine isn't being properly instantiated. Remember folks, what's intuitive to you is a complete mystery to someone who's never brewed that particular blend before!

Ah yes, the tea bag floating on top instead of steeping properly—exactly how features work without documentation. Developer thinks it's "common sense" that you're supposed to remove the staple and dunk the bag. User just plops the whole thing in and wonders why their experience tastes like disappointment and metal. Six months later, the same developer will stare at their own code wondering what dark magic they were attempting.

Developer: "Tea bags are so intuitive they don't need instructions." End user: *dunks entire tea bag, wrapper and all, into hot water* And that's why we write documentation for even the most "obvious" features. Users will find ways to break your software that you couldn't imagine in your worst fever dreams. The line between intuitive and incomprehensible is thinner than your project deadline.

Every dev has said it: "It's so intuitive, why waste time documenting it?" Fast forward six months, and you're staring at your own code like it's hieroglyphics written by a caffeinated squirrel. That tea bag floating in water is the perfect metaphor - what seems crystal clear to you now becomes a murky, unidentifiable mess for the poor soul (probably future you) who has to figure out what the hell you were thinking. Documentation isn't for today's genius you; it's for tomorrow's confused you who just wants to go home.