The Imposter Syndrome Interview
Description
A two-part meme featuring a sad-looking ginger and white cat being interviewed. Above the image, a text exchange is shown. 'Them: How long have you been programming?'. 'Me: Since high school'. 'Them: So you're a good programmer?'. The first panel shows the cat looking downcast as a microphone is held to its face. The second panel is a close-up of the cat's face, now with tears welling up in its eyes, looking profoundly sad. A watermark for 't.me/dev_meme' is visible at the bottom. This meme powerfully illustrates the concept of imposter syndrome in the tech industry. Despite having years of experience (since high school), the direct question about being 'good' triggers a crisis of confidence. For many developers, the more they learn, the more they realize how much they don't know, making 'good' feel like an impossible standard to claim
Comments
7Comment deleted
After 20 years, 'good' just means you know which Stack Overflow answer will fix the bug and which one will summon a Cthulhu-level dependency conflict
Interviewer: “18 years of experience? Perfect - just whiteboard a lock-free queue, annotate the memory barriers, and prove it’s wait-free.” Me: *cat’s second face* suddenly remembering the last decade was 90 % Jira, 10 % YAML
After 20 years in the industry, I've learned that 'programming since high school' could mean anything from 'I've architected distributed systems at scale' to 'I've been copy-pasting from Stack Overflow since jQuery was cool and my git history is just variations of 'fixed stuff' commits.'
Ah yes, the classic 'years of experience' metric - the tech industry's equivalent of measuring code quality by lines written. I've been writing code since high school too, which apparently qualifies me as an expert in jQuery, Flash ActionScript, and confidently breaking production on Friday afternoons. The real question isn't how long you've been programming, it's how many times you've rewritten the same authentication system because 'this time it'll be different.' Spoiler: it never is, but at least now I know enough to be appropriately terrified when someone asks if I'm 'good' at it
Hiring by YOE is like measuring throughput by uptime - looks fine until you check the error budget and pager history
Been coding since high school; good? I’m senior enough to answer “it depends” and ship behind three feature flags with a rollback script named oh-no.sh
20 YoE: one year of knowledge, repeated 20 times with escalating merge conflicts