• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle



  • Let me know if you find one that uses AI to find groupings of my search terms in its catalogues instead of using AI to reduce my search to the nearest common searches made by others, over some arbitrary popularity threshold.

    Theoretical search: “slip banana peel 1980s comedy movie”
    Expected results in 2010: Pages about people slipping on banana peels, mostly in comedy movies, mostly from the 80s.
    Expected results in 2024: More than I ever wanted to know about buying bananas online, the health impacts of eating too many or not enough bananas, and whatever “celebrities” have recently said something about them. Nothing about movies from the 80s.



  • As someone who has often been asked for help or advice by other programmers, I know with 100% certainty that I went to university and worked professionally with people who did this, for real.

    “Hey, can you take a look at my code and help me find this bug?”
    (Finding a chunk of code that has a sudden style-shift) “What is this section doing?”
    “Oh that’s doing XYZ.”
    “How does it work?”
    “It calculates XYZ and (does whatever with the result).”
    (Continuing to read and seeing that it actually doesn’t appear to do that) “Yes, but how is it calculating XYZ?”
    “I’m not 100% sure. I found it in the textbook/this ‘teach yourself’ book/on the PQR website.”



  • This article is so strange in its discussion of the “cul de sac” that Gilbert wrote into the ending of Monkey Island 2, to “sequel-proof” it deliberately. Rot! For people who haven’t played it, (mild spoilers coming up soon, in just a moment, as soon as I close these parentheses) the final shot of the game literally has the older brother mug the camera (behind Guybrush’s back) while his face morphs back to LeChuck’s ghoulish grin and some decidedly unnatural magical flares and sparks dance around.

    (Spoilers mostly done)

    The entire premise of Guybrush being trapped in an illusion cast by LeChuck was already baked in. And I think that helping Guybrush realize that and to escape could’ve been an excellent first chapter of a third game, but unfortunately the designers decided to basically handwave the whole thing and start the their story back in “reality”.





  • Re: the Acceptance stage.

    Years ago I worked at a family-run business with a good working environment. The staff were once told a story of how, earlier in the company’s history, a manager made a mistake that caused the company a substantial monetary loss.

    The manager immediately offered their resignation, but the owner said to them, “Why would I let you go now? I’ve just spent all this money so you could learn a valuable lesson!”

    So yeah, generally, most managers’ reaction to accidentally deleting vital data from production is going to be to fire the developer as a knee-jerk “retaliation”, but if you think about it, the best response is to keep that developer; your data isn’t coming back either way, but this developer has just learned to be a lot more careful in the future. Why would you send them to a potential competitor?



  • Oh hell, you gave me a PTSD flashback!

    It’s the late 90s. My mother suddenly discovers File Explorer on her refurbished commodity Wintel box and decides that all this messy clutter has to go. Never mind that the drive was 80% empty when delivered and I didn’t expect her to come close to filling it before it was replaced. Fortunately I had already backed up everything that looked important or interesting.

    One day she calls from the office, “I don’t need this ‘Windows’ any more, do I?”

    “What? Wait! Don’t do anything!” I walk in and she’s got C:/Windows highlighted and the cursor is hovering over “Delete”.

    “I already have Windows installed on this computer, so I don’t need this any more, do I?” Spoken more as a statement than a question. It took several minutes of forced calm explanation to get her to accept that this “Windows” directory WAS the Windows that’s installed on the machine. She still wasn’t happy that she could see it in File Explorer, though. So untidy!




  • I tought myself programming as a kid in the 80s and 90s, and just got used to diagnostic print statements because it was the first thing that occurred to me and I had no (advanced) books, mentors, teachers, or Internet to tell me any different.

    Then in university one of my lecturers insisted that diagnostic prints are completely unreliable and that we must always use a debugger. He may have overstated the case, but I saw that he had a point when I started working on the university’s time-sharing mainframe systems and found my work constantly being preempted and moved around in memory in the middle of critical sections. Diagnostic prints would disappear, or worse, appear where, in theory, they shouldn’t be able to, and they would come and go like a restless summer breeze. But for as much as that lecturer banged on about debuggers, he hardly taught us anything about how to use them, and they confused the hell out of me, so I made it through the rest of my degree without using debuggers except for one part of one subject (the “learn about debuggers” part).

    Over 20 years later, after a little professional work and a lot of personal projects and making things for other non-coding jobs I’ve had, I still haven’t really used debuggers much. But lately I’ve been forcing myself to use them sometimes, partly to help me pick apart quirks in external libraries that I’m linking, and partly because I’d like to start using superscalar instructions and threading in my programs, and I remember how that sort of thing screwed up my diagnostic prints in university.