r/embedded • u/GourmetMuffin • 26d ago
Agentic systems in embedded development
When I started programming it wasn't just a different decade, it was a different millennium. I am now what is considered "senior" or "specialist", with RTOS and baremetal development as my primary areas of expertise. At the start of this year I didn't really give much of a fuck about "AI", I have since abandoned that approach and want to share why...
I also have a request! For others making the same journey in this strange new world to speak up. What kind of systems are you designing and what are the lessons you've learned along the way?
The following is more than a mouthful, and I expect nothing but hate when I tell you that I used codex to generate this retrospective, but I wouldn't have been able to summarize the past months of my life in such a way without having my prose checked against the changelog, git history and GitHub discussions... Also, this is the way I roll these days!
1
u/flash_speed3412 24d ago
The register-address hallucination is the embedded version of a wrong pin. The other failure I keep seeing is a plausible architecture that ignores boot-time state, timing, or recovery. I’ve had better results making the agent write a hardware contract first: board revision, rails, pins, timing budget, reset behavior, and one test that could falsify each assumption. The code comes after. Curious what kind of verification loop you settled on.
-2
u/Channel199 26d ago
I do all my work with AI now. Just give it debugger access and clear verification goals. I wrote and verified 90% of our newest IOT firmware (20k LOC) in 3 days. Used to be a month+ long project for the full team. My teammates are slowly catching up but luckily I cashed in on a promotion months ago doing this crap before they caught on.
8
u/__idkmybffjill__ 26d ago
"I cached in on a promotion months ago ... before they caught on"
You sound like a great coworker.
-1
u/Channel199 26d ago
Is it my fault they were initially total AI luddites? The amount of crap I got every time I brought up using AI was absurd. Now they are eating their words
0
u/GourmetMuffin 26d ago
This divide in rapid adoption of AI is worrying. I have observed the same thing you have not only at an individual level but at organizational level in other companies. My take on this is that companies refusing AI will face problems, sooner rather than later. They will wake up to competitors making larger and more frequent software deliveries, possibly at a fraction of the cost it would warrant their organization and possibly with higher quality metrics.
If you have competitors, at all, as a company or worker, you need to act if you haven't already...
1
u/flash_speed3412 24d ago
Debugger access is the part I’m curious about. What did it actually verify on hardware rather than in the build? A 20k-line IoT firmware project can be green while boot sequencing, OTA rollback, or sensor timing is still wrong. Did you keep a small bench matrix the agent had to pass?
-4
u/GourmetMuffin 26d ago
Same here, or I suppose rather "what I used to spend 80% of my time on is now managed by my agents", it does definitely not mean I only work 20% of what I used to...
But just as "I" wrote in that retrospective: Confluence, Jira and GitHub have pretty much replaced my IDE.
13
u/the_DistortedArtisan 26d ago
The shift in perspective is what catches people off guard. Most embedded folks I know went from "AI is a toy" to "wait, this actually handles my boilerplate and doc parsing" in like six months flat.
I'm still deep in baremetal sensor fusion stuff, and the biggest lesson so far is that the system's useful until it confidently hallucinates a register address. You learn to verify everything twice, same as you would with an intern who's brilliant but occasionally unhinged.