When your résumé oversells your GitHub and reality crash-lands hard

Description

The meme is a four-panel collage under the Russian caption: "Я в резюме: загляните на мой гитхаб, там шикарные проекты Мои проекты:" which translates to "Me in the résumé: check out my GitHub, there are gorgeous projects My projects:". Each panel shows a hilariously photoshopped, obviously non-airworthy airplane: top-left a jet with a gigantic intake replacing its fuselage, top-right an absurdly bloated Airbus A380, bottom-left a plane with dozens of engines lined across the wing, and bottom-right an impossibly long, pencil-thin Emirates jet. The visual gag equates these bizarre aircraft to the true quality of one’s side projects, contrasting the polished self-promotion of a résumé with the messy reality hiding in a public repo. For developers, it riffs on inflated portfolio claims, GitHub link flexing, and the gulf between promised code quality and the quirky, half-finished experiments that recruiters actually find

Common Tags

DeveloperHumor DeveloperSelfDeprecation Github Career DeveloperReality RelatableDevExperience

Comments

Anonymous ★ Top Pick Recruiter opens my GitHub and finds the aerospace version of my 15-year monolith: a single massive “RefactorSoon()” intake, 42 duplicate engines named LegacyAdapter-v2, and a comically long fuselage of TODOs that still somehow passes CI

Anonymous ★ Top Pick

Recruiter opens my GitHub and finds the aerospace version of my 15-year monolith: a single massive “RefactorSoon()” intake, 42 duplicate engines named LegacyAdapter-v2, and a comically long fuselage of TODOs that still somehow passes CI
Anonymous

Just like that one microservices architecture you built for a todo app - technically impressive, wildly impractical, and definitely not passing any production readiness review, but hey, it shows you can handle complexity, right?
Anonymous

The classic GitHub portfolio paradox: your resume promises microservices architecture with event-driven design patterns and distributed consensus algorithms, but your actual repos reveal three abandoned React tutorials, a half-finished todo app with 47 console.log statements still in production code, and that one project from a bootcamp that you forked but never actually modified. The Antonov An-225 of ambition meets the regional jet of execution - at least until the interviewer asks you to explain how your 'scalable distributed system' handles more than two concurrent users
Anonymous

Post-merge refactor: extract the BelugaXL before your CI pipeline needs its own tarmac
Anonymous

The README looks A380‑polished, but the code flies by brute force: a 200k‑line monolith duct‑taped to 40 “microservices” and a flock of sidecars - CI is all thrust, architecture provides no lift
Anonymous

The résumé says “cloud‑native microservices at scale”; the repo is one gargantuan dependency acting as the turbofan, 47 tiny engines named services, and a 10k‑line core that spans the runway - beautiful diagrams, zero SLOs, and the only thing that really scales is the README
@qtsmolcat 3y

*visible confusion*
@furqan 3y

TF?
@Infinitelineman 3y

excuse me, but where is the translation? this post violates this channel's rules kekw
@saidov 3y

You forgot to translate
@saidov 3y

“Me in my CV: check out my GitHub, it’s some brilliant work out there. Meanwhile my projects:”
@RinStar2770 3y

So true
@s2504s 3y

It's life
@ashutka 3y

why post russian memes?
1. dev_meme 3y
  
  That was kinda mistake actually Even tho meme is a funny one
@sylfn 3y

please use English in this chat