5 ms·

Chill Winston! Artists in residency are not know for being technical. They are not divas demanding support but individuals who are supposed to have access to re

Chill Winston! Artists in residency are not know for being technical. They are not divas demanding support but individuals who are supposed to have access to resources, space, and support that allows them to develop as artists. The spaces they are working with often benefit from having talented creatives but this isn't a performance gig we're talking about.

darkwater 1y ago
I think it was just an example. The real meat behind the example is what someone said today and that I'm now stealing: AI helps with a faster tech debt generation. Having $anyone asking for $anything in a hurry it's probably the #1 cause of tech debt. If now with AI all the answers are going to be "yes, sure!" well, tech debt will go up.
- jcelerier 1y ago
  the answer was "yes, sure" before AI too. the difference is whether you're going to do overtime staying up to 2AM trying to make things work.
  - darkwater 1y ago
    Not in my case. But overstaying, at least here in Europe, is not seen as a good thing, while using AI starts to be encouraged by CTOs and CEOs.
    - jcelerier 1y ago
      as someone from France this has really, really not been my experience when I think of how many times I had to pull on all-nighters for work because of $deadline.
- Espressosaurus 1y ago
  That's a good way of putting it. Especially in inexperienced users' hands. I'm working with a bunch of autonomy guys (think PHD algorithms people) and ChatGPT lets them write code. Which is good. Except the code is hot garbage. It works for the thing they're trying to do, but it doesn't handle errors, it's not extendable, it's not maintainable, and they'll fight you when you tell them how to make it any of the above because they didn't write it and don't really understand how it works. There's no management buy-in--startup, so velocity matters more than anything--so I've resorted to letting them have their working garbage patch and I just let them deal with the consequences. Frustrating, but quality doesn't matter sometimes.
alterom 1y ago
>Artists in residency are not know for being technical. They use the technology, they make the decisions about technology (like which cameras to use), and they literally can't do their work without the tech — — they better be at list a little "technical" for their own sake. The idea of knowing your gear has nothing to do with artistry. This is my rifle. There are many like it, but this one is mine. And if they're "not known for being technical", they better consult someone who is (that is, you) before making decisions about technology (like choosing equipment for the job). The problem here wasn't their lack of technical expertise. The problem was the artists suddenly showing up one day with strange equipment. The solution here is asking the artists to check in with you about gear as soon as they are signed up, and talking to you BEFORE getting new gear. That's it. They don't have to be more technical. They need to help you help them. You said it yourself that this would not have been a problem for you without Claude if you had more time to deal with it. The problem was a lack of advance warning. And it's a solvable problem. These artists might not have been divas before that residency. But the policy of not having to consult the tech before bringing in gear and expecting it to just work, on zero notice, while remaining "not technical" — that turns them into divas. If they are not making these demands, who does? If that's you, that sounds rather masochistic. In which case using Claude to dull the pain seems rather counterproductive in the short term. Seriously though, Claude isn't a solution for setting expectations and communication, which is the real problem here. You could've still used Claude to write that driver. But you could have also had the several days to do it, and it wouldn't be an example of Claude saves the day any more. Or — better yet — you could've given the artists a chance to reconsider their gear choices. There might not have been a reason why they picked that gear in the first place instead of one you could've worked with easily (did you ask?). You didn't enable the artists to do their job. You enabled them to make uninformed gear decisions. That's not helping them in the long term; it's just setting them up for failure. Claude can't code around an API that isn't there, or a hardware incompatibility. And that's before we get to the most important aspect of art: limitation breeds creativity. This sort of babysitting isn't helping the art either. If the goal is to help them develop as artists, then it seems you're accomplishing the opposite. Have you at least told them that they've created a problem for you? They'd want to know that. People usually don't want to create problems for others. As for me — I'm chill AF in the first place; and I'm not against using chatbots to solve problems — it's just that I'm not convinced that Claude is the right LLM to use here. Perhaps asking ChatGPT about this situation, and how to talk to artists (and shape the equipment policy for your space) would do much more impact on the problem you said is recurring on a weekly basis than using Claude to put more bandaids on a pile of bandaids.

darkwater 1y ago

I think it was just an example. The real meat behind the example is what someone said today and that I'm now stealing: AI helps with a faster tech debt generation. Having $anyone asking for $anything in a hurry it's probably the #1 cause of tech debt. If now with AI all the answers are going to be "yes, sure!" well, tech debt will go up.

jcelerier 1y ago
the answer was "yes, sure" before AI too. the difference is whether you're going to do overtime staying up to 2AM trying to make things work.
- darkwater 1y ago
  Not in my case. But overstaying, at least here in Europe, is not seen as a good thing, while using AI starts to be encouraged by CTOs and CEOs.
  - jcelerier 1y ago
    as someone from France this has really, really not been my experience when I think of how many times I had to pull on all-nighters for work because of $deadline.
Espressosaurus 1y ago
That's a good way of putting it. Especially in inexperienced users' hands. I'm working with a bunch of autonomy guys (think PHD algorithms people) and ChatGPT lets them write code. Which is good. Except the code is hot garbage. It works for the thing they're trying to do, but it doesn't handle errors, it's not extendable, it's not maintainable, and they'll fight you when you tell them how to make it any of the above because they didn't write it and don't really understand how it works. There's no management buy-in--startup, so velocity matters more than anything--so I've resorted to letting them have their working garbage patch and I just let them deal with the consequences. Frustrating, but quality doesn't matter sometimes.

alterom 1y ago

>Artists in residency are not know for being technical. They use the technology, they make the decisions about technology (like which cameras to use), and they literally can't do their work without the tech — — they better be at list a little "technical" for their own sake. The idea of knowing your gear has nothing to do with artistry. This is my rifle. There are many like it, but this one is mine. And if they're "not known for being technical", they better consult someone who is (that is, you) before making decisions about technology (like choosing equipment for the job). The problem here wasn't their lack of technical expertise. The problem was the artists suddenly showing up one day with strange equipment. The solution here is asking the artists to check in with you about gear as soon as they are signed up, and talking to you BEFORE getting new gear. That's it. They don't have to be more technical. They need to help you help them. You said it yourself that this would not have been a problem for you without Claude if you had more time to deal with it. The problem was a lack of advance warning. And it's a solvable problem. These artists might not have been divas before that residency. But the policy of not having to consult the tech before bringing in gear and expecting it to just work, on zero notice, while remaining "not technical" — that turns them into divas. If they are not making these demands, who does? If that's you, that sounds rather masochistic. In which case using Claude to dull the pain seems rather counterproductive in the short term. Seriously though, Claude isn't a solution for setting expectations and communication, which is the real problem here. You could've still used Claude to write that driver. But you could have also had the several days to do it, and it wouldn't be an example of Claude saves the day any more. Or — better yet — you could've given the artists a chance to reconsider their gear choices. There might not have been a reason why they picked that gear in the first place instead of one you could've worked with easily (did you ask?). You didn't enable the artists to do their job. You enabled them to make uninformed gear decisions. That's not helping them in the long term; it's just setting them up for failure. Claude can't code around an API that isn't there, or a hardware incompatibility. And that's before we get to the most important aspect of art: limitation breeds creativity. This sort of babysitting isn't helping the art either. If the goal is to help them develop as artists, then it seems you're accomplishing the opposite. Have you at least told them that they've created a problem for you? They'd want to know that. People usually don't want to create problems for others. As for me — I'm chill AF in the first place; and I'm not against using chatbots to solve problems — it's just that I'm not convinced that Claude is the right LLM to use here. Perhaps asking ChatGPT about this situation, and how to talk to artists (and shape the equipment policy for your space) would do much more impact on the problem you said is recurring on a weekly basis than using Claude to put more bandaids on a pile of bandaids.