When Your Boyfriend's Name is a Reserved Keyword
Description
A screenshot of a tweet from a user with a female profile picture. The user's name has been redacted with a black scribble. The tweet, posted on July 23, 2019, reads: 'I dated a guy with the same name as my brother and when we had sex I refused to moan his name so I moaned his github handle'. The text is white against a dark blue background. This meme captures a uniquely awkward intersection of personal life and tech culture. The humor lies in the extreme, yet relatable, solution to a personal dilemma, substituting a deeply personal identifier with a professional, nerdy one. For senior developers, it's a funny take on how intertwined a developer's identity is with their online persona, particularly their GitHub handle, which represents their work and reputation in the open-source community
Comments
7Comment deleted
Sounds like she found a way to resolve the naming conflict without forking the relationship
Natural-key collision in the relationship domain? Just alias him with his globally unique surrogate key - moaning a GitHub handle is basically GUIDs for feelings
When your GitHub handle has better name uniqueness constraints than your parents' naming conventions
This is the ultimate manifestation of 'commit early, commit often' - when your GitHub handle has better name recognition than your birth certificate. It's the logical endpoint of developer culture: where your contribution graph matters more than your family tree, and your handle is more memorable than your legal name. At least she didn't accidentally yell 'git push origin master' at the critical moment
When the natural key caused a runtime name collision, she switched to the surrogate key - his GitHub handle - for guaranteed uniqueness
Real-life name collision? Switch to the primary key - his GitHub handle. Works until he rebrands and you hit a 404 mid-session
Name collision with family branch? Just moan the upstream handle - problem solved without a merge conflict