AI is useful and scary good

Me:
I have a png. black lines with transparent background. Can you help write python code to make the black lines slightly more thick please?

Claude:
Yeah, here's the python file. 

Me:
Ah, can you just run it for me? I've attached the file image, it's a turtle.

Claude:
I've run into an error. I can't find the file's name.
(keeps thinking)

It seems like I can't directly access the uploaded file through the analysis tool. This might be a limitation of how files are handled in this environment. Let me think of alternative approaches:

  • I could create an HTML artifact that allows the user to upload the image and process it in the browser
  • I could provide them with JavaScript code they can run locally

I think the best approach would be to create an interactive HTML artifact that lets them upload their image and see the result processed in real-time.

Me:


Claude:
Here's the tool you can upload your file to.
(and then I upload the turtle)
--

Yikes, this is good.
I've been using Claude to generate scripts to do tasks that would otherwise take me a while to do, but this one was scary good.

Software jobs are going to change so much. This was just a 300 line tool AI made that was genuinely useful for me. But as soon as this thing can start holding significantly larger context windows and is able to verify results that it produces, it'll no longer just be a tool.

Comments

Post a Comment

Popular posts from this blog

Shake It Up | Time to leave BigTech

tl;dr: I am a senior software engineer, and I know I can easily do this work for the rest of my life. So, it's time to shake it up. - Big tech "levels" people, putting them in categories of seniority. I've reached the "terminal" level at BigTech - the Senior Software Engineer. A place where a significant number of software engineers spend their lives. I know for a fact that I can do this work at this level for the rest of my life. The tech industry has* jobs at this level. Given where I am today, a 30 year old with limited responsibilities, I have the freedom to shake it up.  Join a startup, change my role, start all over, work as a barista, work at a farm. The worst that I can do is stay where I am, that is, continue with my current team. Slightly better is to change within BigTech, but I'm pretty confident it'll be the same problems any team I switch to. So, I must shake it up. Do something where I don't know what that future will be.  I can al...
Continue reading »

Growth at BigTech

Growth at my time at BigTech meant several things to me: Become the person everyone in my working radius knows. Be responsible for a good chunk of work, and in turn get promoted for it. Learn how a big org works, and learn to be effective in them. Eventually be in the room that leaders make decisions. Based on these metrics for growth, here's what I learned you need: Visibility. Visibility Visibility. Assuming you're already a top tier engineer, a team lead, and a go-to person in your project, here's how you get visibility: Be where leaders are. Don't try to play the ladder game from a remote office. It's futile. It's like trying to climb an extra greasy ladder. You will eventually get up there, but no one will recognize nor reward you for having climbed the greasy variant. Look where leaders are looking. Don't work on things you think are important. Don't work on things your users think are important. Work on things leadership thinks are important. T...
Continue reading »

P(ai)r Programming

Over the last 2 months with Claude Pro I've reached the point where I work with AI the way I work with humans. I'm working on a fairly non-standard app - it's got a long living foreground service and interacts with the device from that service. And I'm surprised how helpful it has been for this non-standard use case. Simple tasks First, for simple tasks, I tell the AI what to do and ask it explicitly not to write code. We first review what it's going to do before letting it code. It takes us about 2 to 3 iterations, and then it codes. For most tasks, it's really good. The reviewing started as a way to work around Claude's tight token limit, but now it's just a really good tool to make sure Claude and I are on the same page. This is exactly what I do at work with my team. Every meeting is us writing high level bullets of what they will work on, and once we're on the same page, I just review their code - which usually takes them 1-2 days to come back w...
Continue reading »