CodeQuality
Post #1355 · source on Telegram
Code Formatting Perfection
Description
A three-panel meme using 'The Rock Driving' format. In the first panel, Dwayne 'The Rock' Johnson is in a car and asks, 'Do you use code formatting tools?'. In the second panel, the girl in the back seat replies, 'I used to, but nothing changed.'. The final panel shows The Rock looking back at her with a shocked and horrified expression. The joke implies that the developer's code is already so perfectly formatted that automated tools have no changes to make, a feat of consistency that is both impressive and slightly terrifying to experienced engineers who rely on such tools to maintain standards across teams
More like this
More like this in CodeQuality →
Use J and K for navigation
Comments
7Comment deleted
Some engineers spend hours configuring Prettier and arguing about trailing commas. Others are apparently just born with a built-in abstract syntax tree formatter
We wired Prettier into pre-commit, pre-push, and CI; turns out the only unformatted layer left was Layer 8
She's the same developer who disabled ESLint because it kept throwing errors about unused variables in her perfectly working code that definitely needed all 47 imports
Ah yes, the classic 'Schrödinger's Formatter' - simultaneously configured in the repo and completely ignored by the team. It's like having a state-of-the-art CI/CD pipeline that fails on formatting violations, yet somehow every PR still has mixed tabs and spaces. The real question isn't whether the formatter works, it's whether anyone actually committed the .prettierrc to the repo or if everyone's still running with their own local 'preferences.' Nothing says 'mature engineering organization' quite like a 47-comment thread debating whether to use 2 or 4 spaces while the formatter sits there, perfectly capable of making that decision irrelevant
If your formatter produces a zero‑diff, either you’ve achieved whitespace nirvana or your pre-commit hook never ran - and the odds heavily favor the latter
Running the formatter in --check and wondering why nothing changed is the codebase equivalent of running migrations with --dry-run and calling it deployment
Senior dev privilege: Prettier scans your PR and humbly reports 'no changes' - zero diffs, maximum smug