DevCommunities
Post #4105, on Jan 26, 2022 in TG
When users assume every developer can magically troubleshoot their malfunctioning office printer
Description
The image is a dark-theme screenshot of a Reddit r/AskReddit thread. The post shows an orange up-arrow with “33.4k” and the question text: “What’s something very rare that people think is very common?”. Underneath, the action bar displays “24.3k Comments”, “Award”, “Share”, “Save”, “Hide”, and “Report”. A highlighted top comment from user “CopperyMarrow15” reads: “A programmer who knows how to fix your printer.” with a single up-vote and standard reply/share controls. The meme pokes fun at the widespread misconception that software engineers double as on-call printer technicians, illustrating the communication gap between programming expertise and everyday IT support expectations
Use J and K for navigation
Comments
23Comment deleted
“Sure I’ll fix the printer - let’s refactor its firmware into microservices, put CUPS behind an API gateway, and add Prometheus metrics so we can finally observe which Schrödinger paper-jam you’re blaming me for.”
After 20 years of distributed systems architecture, I can orchestrate microservices across continents with five-nines uptime, but when the office printer shows 'PC LOAD LETTER', I quietly update my LinkedIn status to 'exploring new opportunities' and slip out the back door
Twenty years of distributed systems experience and the printer still wins - it's offline, except it isn't, except it is
The eternal struggle: you can architect distributed systems handling millions of transactions per second, implement complex algorithms, and debug race conditions in concurrent code - but the moment someone discovers you're a programmer, you're suddenly expected to be the printer whisperer, router reset specialist, and family IT helpdesk. Bonus points if they're shocked when you admit you just Google 'PC LOAD LETTER' like everyone else
I can make Kafka exactly-once; your inkjet does at-least-twice, sometimes-never over SMBv1 with a 32‑bit TWAIN driver - fixing it is less software engineering and more archaeology
Rarer than a leak-free custom allocator: the C dev who debugs printers without percussive maintenance
I can debug race conditions; your printer runs a three‑party consensus of driver, spooler, and gremlin - no public API, no SLA
Which kind of fixing? Comment deleted
The one that can enter the hidden menu on it, see that even the diagnostics screen crashes when trying to make a scan, notices that not even the power button is responding anymore. Solution: The oil was hardened so much, the scanner's "sensor array" was frozen in place. What caused a bug, normally the printer moves these kind of sensors until they count the proper amount of the laser that lights trough a transparent plastic that has a bunch of very small lines on it. This is what the printer can count where the head/scan-sensor is. As physics is not instant the printer just adds power to the motor and cuts it when the amount of light interrupts happen. So basically this is a bug that will cause the printer to be in an infinite loop. Comment deleted
Sounds really rare and crazy. I have fixed several printers in 2016 and 2017 when I had another job. Now I'm DevOps but I still can repeat these operations. Does DevOps count as a programmer? Comment deleted
My 20 y.o printer that just work: *Insert monsters inc pic here* Comment deleted
Funny. Before switching to coding i was working for several years as copier technician. And was a good one. So, yeah, im a programmer, who can fix printer, copier or even engineering system (A0 copier). Comment deleted
I'm a programmer and I don't even know how to program. Comment deleted
then how are your a programmer? Comment deleted
understanding programming memes != programming Comment deleted
We must report them! Comment deleted
Not sleeping well? Comment deleted
Just finished with work for today Comment deleted
Sounds great Comment deleted
Programmer: Restart the printer Comment deleted
The printer errors actually usually go like “Error XXX: YYY. Please restart the printer. Contact support if the error occurs again” Comment deleted
I see. However, the users usually didn’t read the prompt message. Sounds silly, but… Comment deleted
have you tried restarting them ? yes ? well than, i can't help you, call support Comment deleted