The Original Tech Support Trick From 1983

Vintage computing Tech support Debugging tricks 1980s computers Reboot fix Legacy-systems Hardware excuses It troubleshooting

Programming Debugging Hardware

1 year ago 259,539 views 0 shares

The Original Tech Support Trick From 1983

vintage-computing-memes, tech-support-memes, debugging-tricks-memes, 1980s-computers-memes, reboot-fix-memes | ProgrammerHumor.io

The classic "have you tried turning it off and on again" tech support trick dates back to the Jurassic period of computing! When a developer loses their cursor in 1983, they immediately resort to the oldest trick in the book—faking a hardware problem and suggesting a reboot. The best part? It actually works, and the comic perfectly captures that smug satisfaction when your BS technical explanation saves the day. Some programmer traditions never die, they just get faster processors.

More Like This

Someone said “wait until he finds about Apple tax” the day he started talking about Twitter Blue. I guess today’s the day.

Programming Apple

2 years ago 77.6K views 0 shares

Someone said “wait until he finds about Apple tax” the day he started talking about Twitter Blue. I guess today’s the day. | developer-memes, iphone-memes, apple-memes, twitter-memes | ProgrammerHumor.io

Content Elon Musk elonmusk Spoiler alert Did you know Apple puts a secret 30 tax on everything you buy through their App Store? Watcher.Guru WatcherGuru 6h Replying to elonmusk Apple takes a 30 tax from app developers who make over 1 million through the App Store on an annual basis. Apple's App Store is the equivalent to a 30 t... 00:20 - 291122 . Twitter for iPhone

Choose carefully

Programming

3 years ago 57.6K views 0 shares

Choose carefully | ProgrammerHumor.io

Content "Your safe word must be at least 8 characters in length and contain one uppercase, one lowercase, one number and one special character"

Don't Need Fix Need Answers

Programming Debugging Testing

1 month ago 229.9K views 0 shares

Don't Need Fix Need Answers

You know what's worse than not being able to fix a bug? Being able to see exactly what's wrong in the bug report but having absolutely zero clue how the code even produces that error in the first place. Like, the error message is crystal clear, the stack trace points right at the problem, but when you open the codebase it's like staring into the void. You're not even asking "how do I fix this?" anymore—you're asking existential questions like "how has this ever worked?" and "who wrote this?" (spoiler: it was you six months ago). The bug report is a map to treasure, except the treasure is buried in a codebase held together by duct tape and prayers.

Limited Rekognition

Programming

1 year ago 60.0K views 0 shares

Limited Rekognition | ProgrammerHumor.io

Content MACHINE LEARNING Daddy (Daddy (Daddy (Daddy whYatt

That would be great

Programming Javascript StackOverflow Linux

4 years ago 177.2K views 0 shares

That would be great | json-memes, overflow-memes, sudo-memes | ProgrammerHumor.io

Content Cyris sudooverflow All I want to know is will elonmusk's NeuroLink have an API and can I get my memories in JSON format? 3:50 01 Sep 20 TweetDeck

Studding computer scince

Programming

4 years ago 65.1K views 0 shares

Studding computer scince | computer-memes, tech-memes, computer science-memes | ProgrammerHumor.io

Content Me: Starts studying Computer Science Every person I have ever known: It's Free Tech Support