• 1 Post
  • 7 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • It’s been used many times before, but I like the analogy of ordering food. If I go to a restaurant and order risotto, I haven’t made the dish, I’ve only consumed it. I want you to focus on that word “consume”, it’s important here.

    Another idea I’ve seen recently that I like was a summed post something like this:

    • People use AI to write a 4,000 word article from a 15 word idea (introduction of noise)
    • Others then use AI to summarize the 4,000 word article into a 15 word blurb (introduction of more noise)

    I know I’m using a lot of analogies here; from food to writing and now the visual medium - but stick with me. Completely sidestepping any lofty notions of soul or humanity, let’s look strictly at what’s being communicated in a visual piece of art generated by AI. It’s an idea, one containing neither your specific style (the creative process) or vision (the final product), though you may feel you get a close approximation after several iterations and a detailed/complex enough prompt. If you wanted to convey the idea of “eagle perched in a tree”, you’ve already done so with that phrase (or prompt in this respect). By providing an AI-generated image, you’ve narrowed my own ability to interpret down into the AI-generated noise now taking up space between us.

    The reason you’d use AI-generated art is because you need to fill space, like the thumbnail to go with an article. An empty space to dump things into. While I can’t ever claim enough authority to define what exactly art is and is not (nobody can), I can say with absolute certainty that no matter how far the tech evolves, to me PERSONALLY, AI will only ever generate content, not art. There is already more art in the world than I could possibly consume in a hundred lifetimes, I neither want nor need this garbage.



  • 1000% this. Without giving away too much information, I work(ed) for a cloud provider (not one of the big ones, there are a surprising number of smaller ones in the field you’ve probably never heard of before). I quit this week to take a position in local government with some quaint, on-prem setup.

    1. We were always understaffed for what we promised. Two guys per shift and if one of us took vacation; oops, lol. No extra coverage, just deal.
    2. Everyone was super smart but we didn’t have time to work the tickets. Between crashes, outages, maintenance, and horrendous tickets that took way too much work to dig into, there was just never enough time. If you had a serious problem that took lengthy troubleshooting, good luck!
    3. We over-promised on support we could provide, often taking tickets that were outside of infrastructure scope (guest OS shit, you broke your own server, what do you want me to do about it?) and working them anyway to please the customer or forwarding them directly to one of our vendors and chaining their support until they caught wise and often pushed back.
    4. AI is going to ruin Support. To be clear, there will always be support and escalation engineers who have to work real problems outside the scope of AI. However without naming names, there’s a big push (it’ll be everyone before too long, mark it) for FREE tier support to only chat with AI bots. If you need to talk to a real human being, you gotta start dishing out that enterprise cash.

    Mix all that together and then put the remaining pressure on the human aspect still holding things up and there’s a collapse coming. Once businesses get so big they’re no longer “obligated” to provide support, they’ll start charging you for it. This has always been a thing of course, anyone who’s worked enterprise agreements knows that. But in classic corpo values, they’re closing the gap. Pay more for support, get less in return. They’ll keep turning that dial until something breaks catastrophically, that’s capitalism baby.