Thank you :) One of the nice things about working on a game engine is it's actually a large collection of small projects disguised a big one. That let's my squirrel-brain jump from thing to thing and have enough variety to not get bored.
I just started using AI a few months ago. My smoke-test was "can it write a simple memory allocator". Until recently, every time I tried to get an AI to write an arena or simple buddy-style heap allocator, they just vomited all over themselves. To my surprise, the last time I tried, the AI absolutely crushed it; it unearthed tricks I didn't even know about in one shot. Since then, I've been using AIs to do the boring, rote work that effectively just boils down to me typing in something that's in my head. For that, they're great. I typically sketch out the thing I want it to make, then tell it to fill in the blanks. Sometimes they still go off the rails, but all in all it's a useful tool.
Where I've found they still struggle is making any architectural decisions, or where performance matters.. even a little bit. They often make super braindead decisions when it comes to performance for no discernable reason. They'll course correct when you tell them to, but I've had to keep a close eye on the output and reign it in frequently. Asking an AI to design a system from the API level hasn't ever returned a good result for me.. I always do that work.
All in all, I feel like using AI will probably make me a better programmer in the long run, contrary to popular belief. They accelerate the boring stuff I already know how to do, which leaves me with more time to work on the edge of my skill level where I grow as an engineer. Guess we'll see in 5 years.
I just started using AI a few months ago. My smoke-test was "can it write a simple memory allocator". Until recently, every time I tried to get an AI to write an arena or simple buddy-style heap allocator, they just vomited all over themselves. To my surprise, the last time I tried, the AI absolutely crushed it; it unearthed tricks I didn't even know about in one shot. Since then, I've been using AIs to do the boring, rote work that effectively just boils down to me typing in something that's in my head. For that, they're great. I typically sketch out the thing I want it to make, then tell it to fill in the blanks. Sometimes they still go off the rails, but all in all it's a useful tool.
Where I've found they still struggle is making any architectural decisions, or where performance matters.. even a little bit. They often make super braindead decisions when it comes to performance for no discernable reason. They'll course correct when you tell them to, but I've had to keep a close eye on the output and reign it in frequently. Asking an AI to design a system from the API level hasn't ever returned a good result for me.. I always do that work.
All in all, I feel like using AI will probably make me a better programmer in the long run, contrary to popular belief. They accelerate the boring stuff I already know how to do, which leaves me with more time to work on the edge of my skill level where I grow as an engineer. Guess we'll see in 5 years.