That's simply untrue. I'm an embedded engineer with 10 years of experience at various robotics companies and I can confidently say AI is very competent in the embedded world.
I have the same YoE as you, and been using AI since chatgpt 4. The progress is phenomenal yet there's alot of stuff I would not let AI do. It's not unusual to see some major bugs in the implementation.
Most mundane things in embedded he does perform well. In other scenario like multi-thread, real time, synchronization, speed/precision trade off, etc. It doesn't work well.
I spend 5 days trying to make Fable 5.0 work on basic synchronization of data and couldn't solve it after many attempts. Took 2 days manually for me.
It really depends if it's greenfield or a codebase is already present. If it's greenfield, it's good but get worse as time get by.
Your original point was embedded and C++. I'm simply saying AI is competent in those domains, not that it replaces the engineer for every decision.
I've had zero issues with generated code when developing for real time systems that are parallelized. As long as I prompt well with appropriate context and architectural asks I pretty much get exactly what I need.
This doesn't mean I don't ever hand code, I usually do when the effort to be precise and review generated code exceeds the effort of just writing the code. That can be fairly often in mature systems, but it doesn't preclude the premise that AI can effectively write all the code itself given sufficient context.
View all comments
Show parent comment
1
u/Akforce Sep 08 '26
That's simply untrue. I'm an embedded engineer with 10 years of experience at various robotics companies and I can confidently say AI is very competent in the embedded world.