• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle



  • the_toast_is_gone@lemmy.worldtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    3
    ·
    14 days ago

    Preface: If all you want is to get a simple script/program going that will more or less work for your purposes, then I understand using AI to make it. But doing much more than this with it will not help you.

    If you want to actually learn to code, then using AI to write code for you is a crutch. It’s like trying to learn how to write an essay by having ChatGPT write the essays for you. If you want to use an API in your code, then you’re setting yourself up for greater failure the more you depend on AI.

    Case in point: if you want to make a module or script for Foundry VTT, then they explicitly tell you not to use AI, partly because the models available online have outdated information. In fact, training AI on their documentation is explicitly against the terms of service.

    Even if you do this and avoid losing your license, you run a significant risk of getting unusable code because the AI hallucinated a function or method that doesn’t actually exist. You will likely wind up spending more time scouting the documents for what you actually want to do than if you’d just done it yourself to begin with.

    And if the code works perfectly now, there’s no guarantee that it will work forever, or even in the medium term. The software and API receive updates regularly. If you don’t know how to read the docs and write the code you need, you’re screwed when something inevitably gets deprecated and removed. The more you depend on AI to write it for you, the less capable you’ll be of debugging it down the line.

    This begs the question: why would you do any of this if you wanted to make something using an API?








  • I had my Sonata stolen last year. The problem is that, by default, there was neither a key checker nor a steering immobilizer built into the vehicles. These are industry standard features for every car manufacturer… Except Kia and Hyundai. These are required features in every car sold in every Western nation… Except the United States. To have excluded this literal 90s tech from their vehicles when they’re so common that no one would ever stop to think about whether their car has them constitutes a serious lie by omission on the part of Kia and Hyundai, in my opinion. If I knew that all you had to do was rip off the ignition and shove something onto a peg to screw off with the car, I would have told the dealer to stick it up his butt.

    For those wondering: I had comprehensive insurance, so I was paid the full value of the vehicle after it was totaled. I bought a Toyota Camry with the money and it’s a great car. I am never buying Kia or Hyundai cars again and I recommend everyone else avoid them from here on out. Like, if this is what they’re willing to do to save $30 per assembled vehicle, what else might be lurking in their newer vehicles that we won’t know about until it’s too late?





    • Short term interest: this is just human nature. All economic models work around human nature and desires. People desire short-term gains in pretty much any endeavor. If this was a communist society, they’d still rush to get this thing out as fast as possible so they could meet state quotas/meet whatever other incentive is being offered to finish the job. The problem comes not from the motivations, but how they respond to it. Rushing deadlines and ignoring the need for testing and quality code is a universal human constant.
    • Commercial focus: we have a much better idea of how much an endeavor, product, service, etc. will cost under capitalism because we have a decentralized and automatic way to calculate its value in the form of prices. Miscalculations - or simple human errors, like pushing bad code by accident - happen though, and hopefully this company has learned that prioritizing pushing something out can risk losing them money vs. testing it and coming out with a quality product.
    • Antagonist interests: this is another question of short-term vs. long-term interests. Say you have a factory. If you crank up the machines to double speed, you’re potentially doubling your production, right? It isn’t that simple, actually. You can end up with a lot more workplace accidents that way, which will destroy your productivity extremely quickly. Same deal here. This will, hopefully, be a lesson learned by the industry in not pushing garbage code. M$ can’t serve ads to people who can’t boot their PCs, and will instead lose boatloads of money suddenly having to fulfill tech support contracts because of their screw-up, for example. Crowdstrike is going to have its competitors look a lot more appealing from here on out because they’ve been exposed as fools. (If they have no competitors - IT people, this is your sign!) Mistakes will happen until the end of time, of course, but that doesn’t mean fat-fingering the keyboard is a fault of the Western economic system.

    Capitalism is, in essence, the ability for people to exchange their goods freely. It isn’t dependent on corporations or some weird hierarchy of managers and workers. Those are facts of living in this system, but it isn’t a direct consequence of “capitalism.” If everyone worked only for themselves and produced something to bring to the exchange, that would still be capitalism.