A Slight Career Pivot: From Pornstar to Programmer
Description
The image features a smiling woman in what appears to be a modern kitchen or bar area. She is holding a black coffee mug and wearing a black long-sleeved shirt with a humorous, provocative statement printed on it. The text on both the shirt and the mug reads: "CODING saved me from being a Pornstar now I'm just a PROGRAMMER". The words 'CODING', 'Pornstar', and 'PROGRAMMER' are emphasized, with 'Pornstar' and 'PROGRAMMER' highlighted in a bold, orange, outlined font. In the background, there's a bottle of what looks like champagne or sparkling wine and several empty glasses, adding to a celebratory or casual atmosphere. The joke uses a self-deprecating and absurd comparison to comment on programmer identity. For the tech audience, the humor lies in the cynical implication that a career in programming, while ostensibly respectable, can sometimes feel just as thankless, draining, or exploitative as a more notorious profession. It's a commentary on the less glamorous aspects of the tech industry, resonating with the dark humor often found in developer communities
Comments
8Comment deleted
One job involves dealing with poorly documented APIs, legacy systems, and getting screwed over by unseen stakeholders. The other is being a pornstar
Swapped adult entertainment for programming - turns out the late-night contortions just moved from the studio to Kubernetes YAML, and the anonymous spectators are now Grafana dashboards judging my P95
At least in porn, when someone says they want to see your backend, they mean it literally - not spend three hours debugging your microservice architecture only to discover the real problem was a missing semicolon in the legacy monolith
Career pivot validated: both industries involve unrealistic deadlines, awkward standups, and pretending the legacy stuff was shot by someone else
The shirt's message resonates because both professions involve long hours in front of a screen, dealing with demanding clients who want impossible things delivered yesterday, and constantly having to explain that no, you can't just 'make it work' without proper requirements. At least in programming, the only thing getting screwed is your sleep schedule and the production database on Friday deployments
From objectifying bodies to object-oriented bliss - at least now the inheritance drama stays in the family tree
Swapped being on camera for being on call - still judged on performance, but now when something leaks it’s memory, not a GDPR incident
Different industry, same performance obsession - just moved from “no buffering” to chasing 95th‑percentile latency, and the director is now an SRE