• 0 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle













  • Many years ago, my aunt bought an old, terribly specced laptop and couldn’t get Windows to run on it. I installed Ubuntu and everything was fine - she could check her email and browse toxic conspiracy theories on Facebook and all was good with the world.

    Two years later when visiting I got my first support request - would I mind showing her how to print something? No problem, but would you mind showing me what you were trying? She was selecting menu items to send to a virtual printer, not the one on the network. I show her the correct printer to send to and the thing prints. Easy. Out of curiosity, I check the outbox queue for the virtual printer. Over a hundred documents, going back two years.

    For two years she’d been unable to print, and every single time she’d ever attempted to print something she’d followed the exact same steps that didn’t work, and just accepted that this was the way things were.

    SMH.




  • I know you’re playing the straight man to a joke, but actually you can apply a linter, then tell GitHub to ignore the implied ownership history for the purposes of blame from that reclining pr. All such prs are massive and yet by virtue of the replayability of the linter it’s also very easy to ensure errors didn’t slip in when reviewing.

    I know the original comment was about renaming all the variables, but that’s obviously deliberately absurd, so I’m using here a completely realistic example instead.