The Duality of a Developer's GitHub Profile
Description
A two-panel meme using an image of performance artist Vermin Supreme (with a boot on his head) next to a serious-looking man in a suit. The eccentric figure on the left is labeled 'my private LISP-oriented part of Github', representing a developer's quirky, non-commercial, or esoteric passion projects. The professional figure on the right is labeled 'me showing public contributions to Kubernetes', symbolizing the polished, career-focused, and mainstream open-source work that is displayed publicly. The humor lies in the stark contrast between the public-facing professional persona and the private, often weird, coding hobbies. It highlights the tension between contributing to popular, resume-building technologies like Kubernetes and tinkering with niche, academic, or older languages like LISP
Comments
7Comment deleted
My GitHub is basically a mullet: business in the front with all the Kubernetes and Terraform commits, party in the back with private LISP and Forth repos that nobody, especially a hiring manager, should ever see
My GitHub’s a wall of green squares from tweaking Kubernetes YAML, but in a private repo a 15-line Lisp macro quietly generates the whole cluster - resume-driven development as performance art
My GitHub graph shows 10,000 commits to YAML files while my soul quietly implements the Y combinator in a language that hasn't had a job posting since 1987
Every senior engineer has that one private repo where they're building a LISP-based distributed system 'for fun' while their LinkedIn proudly displays their Kubernetes CKA certification and 47 merged PRs to helm charts. It's the technical equivalent of being a classically trained pianist who secretly produces death metal in their basement - both require deep expertise, but only one gets you past the recruiter screen
Kubernetes earns the stars, but that private Lisp REPL orchestrates universes normies call 'impossible.'
Public GitHub: shiny K8s PRs. Private GitHub: Lisp macros that generate the operator that generates the YAML that configures the thing my PR touches - guess which one recruiters notice
Publicly I fix CRDs and bump Operators; privately a 3k-line Lisp macro emits the Helm chart that emits the YAML - parentheses are my best obfuscation layer