this post was submitted on 02 Oct 2024
511 points (97.4% liked)

Programmer Humor

19809 readers
1096 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Benjaben 9 points 2 months ago (1 children)

Yep, I did similar around the time. Can't blame people for being mad that the thing they bought is damn near unusable (and was destined to be, but they didn't understand that part). If someone buys a new bike, even if it's cheap, it shouldn't roll like you're on gravel after a couple weeks and become impossible to pedal within months. But damn, there were a lot of horrible machines sold in those days.

And then of course, the least fun part of that era, the guys who would bring their machines back weekly despite very stern warnings to stop visiting "those sites".

[–] [email protected] 9 points 2 months ago* (last edited 2 months ago) (1 children)

And then of course, the least fun part of that era, the guys who would bring their machines back weekly despite very stern warnings to stop visiting "those sites".

Hey, they were good for business lol

Lady he's putting my kids through college

[–] Benjaben 4 points 2 months ago (1 children)

Definitely not wrong! Especially once you've dialed in your routine of anti-malware utilities to run on pretty much everything. It's like an antibiotic cocktail, lol. Or did you prefer the "back up and nuke on sight" approach?

[–] [email protected] 5 points 2 months ago* (last edited 2 months ago) (1 children)

I'd usually start with my suite of cleanup tools, do some manual cleanup if needed, apply all the software and security updates, and then give it a day with some light test usage. Then I'd re-run the tools to see if they picked anything back up. If not, I released it back to the customer. If anything at all came back, I'd backup their data, pull all the product keys I could (Office, Photoshop, etc), nuke the OS, and reinstall what I could as close to the original as possible.

[–] Benjaben 1 points 2 months ago

Lol yep sounds a lot like my process! Took time to get it down and settle on tools (though those always changed anyway) but once you did, could make a buncha money for sure. With KVMs I could do a lotta volume on those kinda jobs and get some of my engineering homework done in between. Hardware repairs were more fun but way more time consuming and hit or miss depending on overall condition.

Not a bad gig overall but certainly did come with some downsides. Like, desktop computer filled with insect carcasses, brown everywhere with tar from cigarette smoke, stinking up the shop, customer somehow oblivious to the gnar-bomb that is their daily life intersecting with "ordinary" society.