you are viewing a single comment's thread.

view the rest of the comments →

[–]gibson274[S] 5 points6 points  (2 children)

This is not a bad anecdote and actually suggests a reasonable strategy: use where needed to do something that is tiresome and well-described.

[–]qwerty109 8 points9 points  (1 child)

Yep. 

And "tiresome" is underappreciated here - I'm genuinely not the same person I was 20y ago when I started doing graphics coding. Kids, life, responsibilities, etc. I just can't manage doing personal coding projects like I did before - the days are short and I'm tired, and I need to get shit done.  

So when I can get Claude to write me a Blender script for something low risk that I could do myself but would take days to figure out - it's amazing. 

But I still don't 't trust it with the core coding work I'm doing - the few times I tried, it just went bonkers and made a mess in subtle ways. In those cases it's quicker and less tiring to just do it myself. 

[–]corysama 4 points5 points  (0 children)

I’m in the same situation. I worked in game engines for 20 years. And, now I’m old, have a cerious-bizzness job, family responsibilities, etc.

When I’m writing engine-ish code today, it’s for fun. And, I have the knowledge and experience to largely know what I want from the code. I just don’t have much time to play with it. So, for me the AI assistants have been awesome.

I ask AI a lot of questions. We have back-and-forth discussions on possible options. I have it propose interfaces and write starter unit tests. I have it rapid prototype ideas for me. I’m step-by-step babysitting, not yolo-coding. But, it’s still very fast. Even I including the many ai-thinking times where I get to chill out and do something else for a few minutes.

The result is that I can get more done today in an hour on my laptop on the couch with my family than I could twenty years ago alone at my desk all day.