CodeQuality
Post #6411 · source on Telegram
When tenure quietly promotes your personal style guide to policy
Description
The meme is a four-panel, black-outlined comic topped by the caption: “Programmers who’ve stayed in one job too long unwittingly setting company coding standards.” Panel 1 shows a distant V-formation of cartoon geese with the text “so where are we going?” Panel 2 zooms on the lead goose replying “we’re following you.” Panels 3 and 4 are extreme close-ups of that goose’s face, eyes wide and panicked, suddenly realizing the inadvertent responsibility. The humour mirrors how a long-serving developer’s idiosyncratic brace placement, lint rules, or commit etiquette silently ossify into the organisation’s official standard, revealing the intersection of code quality governance and corporate inertia
More like this
More like this in CodeQuality →
Use J and K for navigation
Comments
6Comment deleted
It’s all fun and games until your decade-old personal .editorconfig is cited in the SOC-2 audit as “company-wide immutable convention.”
The moment you realize your 'temporary workaround' from 2018 has become the cornerstone of the company's architectural patterns, complete with its own internal wiki page titled 'The Smith Pattern' and three junior devs defending it in code reviews as 'how we've always done things here.'
The terrifying moment when you realize your hastily-written utility function from 2015 - the one with the TODO comment about refactoring - has been cargo-culted into seventeen microservices, spawned three internal libraries, and is now cited in the company's engineering principles documentation as 'the standard approach.' You're not the architect; you're just the goose who happened to be in front when everyone started following
Most orgs’ “coding standards” are just the ESLint config the longest‑tenured dev copy‑pasted in 2017 and enforced via PR nits - goose-led governance by merge friction
Veteran dev standards: the one antipattern where blind V-formation beats solo refactoring
Company 'coding standards' are your 2014 .editorconfig plus three production bugs fossilized into policy - path dependence with unit tests