People keep asking me, and I haven’t really had an answer, but now yeah, I’m thinking I’m back.

  • 0 Posts
  • 34 Comments
Joined 4 months ago
cake
Cake day: March 18th, 2025

help-circle









  • I’m a big fan of Special K as it effectively fixed Nier Automata on PC for me. Kaldeian has done excellent, thankless work on making PC games work better and for more people.

    And though Valve shouldn’t always be given the benefit of the doubt, I don’t really agree with his arguments.

    Games you purchased on a Windows 98 machine later had their system requirements bumped up to Windows XP, then to Windows 7, then to Windows 10…

    Is there any connection between the hardware your initial purchase was made on, and the hardware you would run that game on right now? You can buy games from your phone, or your Steam deck, or at the public library, or on your father’s Gateway. Maybe he means the game’s original system requirements, as listed “on the back of the box” so to speak. But if I want to play SWBF2 from 2005, must I find an Intel Core 2 Quad Q6600 and an ATI Radeon HD 5570? No, I just need parts with equivalent/better performance that I can find today. Steam updating those system requirements for newer hardware makes those games MORE accessible, not less. It considers new gamers discovering older games and gives them a path to playing it.

    The inexorable passage of time, and the eventual security flaws that can no longer be patched, means that every single one of those devices will be retired. But that’s why emulation and tools like Special K are important to game preservation. It’s why Stop Killing Games is not retroactive and does not ask for infinite software support.









  • I’ve seen lazy developers take solutions from Stack Overflow, and paste them directly into code with no scrutiny, no testing, no validation. I’ve also seen talented developers take solutions from Stack Overflow, verify them, scrutinize them, simplify or expand on them. The difference wasn’t the source of information, but what the developer did with it.

    AI is a crutch for the shameless, careless developers who create more problems than they solve. It’s just made them more efficient at it. Which only creates problems faster than than the talented developers can solve; it’s easy to destroy, but difficult to build. I know talented developers who use AI, but it hasn’t made them faster or more efficient, because their strength is also their weakness: they take their time, they evaluate their options, they scrutinize AI output because they know its prone to mistakes.

    My greatest worry is the folks in the middle - they’re neither experts nor novices, just average. I want to see more engineers develop the skills needed to make them experts, but I worry that AI will just make them lazy.


  • That sounds like treating the symptom rather than the disease. Why automate the toil, when we could remove it instead? The other commenters brought up examples:

    generating (the boring) parts of work documents

    when I notice auto-generated parts, which triggers that I use AI in turn, and I ask it to summarise all that verbose AI generated content.

    The AI wrote a document a human didn’t want to read, so AI then read the document AI wrote. The incentive thereafter is to save, and use, the shorter AI doc over the longer one.

    Was any value created by this cycle? We just watered down the information with more automation. In the process, we probably lost nuance, detail. Alternatively, if we all agreed the document wasn’t worth a human’s eyes or keystrokes in the first place… why have the AI do anything? Sounds like we would all be happier to not have the document in the first place.