Nov 19, 2026 · 35 min · 11 segments
Jacob Beningo talks with RTOS pioneer Bill Lamie, creator of Nucleus, ThreadX, and PX5 RTOS, about how to write efficient, high-performance real-time code. They cover POSIX pthreads, keeping software…
Jacob BeningoHost
Now, I know with your experience working with real-time operating systems and just general embedded systems industry experience, what are some of the design lessons that you've learned over the course of your career so far?
And that's really what kills, you know, all software, but especially embedded systems.
The complexity, you know, if you create complex software, likely that complex software is going to run pretty slow.
So I think, you know, the biggest thing and it's, you know, all of us know this is keep it simple, stupid.

Complexity is definitely, I think, an evil to a lot of designers, developers, and architects.

I actually keep a list of what I consider to be my seven modern embedded software principles.

And number three on the list is kiss the software, which is keep it simple, silly, or keep it simple, stupid, however you want to substitute it.

But every day when I go to write code, I go, all right, what are my principles I'm making sure I'm following? And That one is, like I said, it's in the top seven, top three.

Some other thoughts on things that you've learned that developers, even teams working with real-time operating systems might want to keep in mind?
Yeah, the, you know, so, so keep it simple, but, you know, in practical terms, you know, there's other things too, like function calls kill.
So, you know, if you have, you know, the more nested function calls you have, you know, each one of those eats up tons of performance, you know, pushing, pushing registers on the stack, return address on the stack, doing all that stuff and then popping it back off.
So keeping your function call nesting and the number of function calls down to a minimum is good too.

Now, I know with your experience working with real-time operating systems and just general embedded systems industry experience, what are some of the design lessons that you've learned over the course of your career so far?
And that's really what kills, you know, all software, but especially embedded systems.
The complexity, you know, if you create complex software, likely that complex software is going to run pretty slow.
So I think, you know, the biggest thing and it's, you know, all of us know this is keep it simple, stupid.

Complexity is definitely, I think, an evil to a lot of designers, developers, and architects.

I actually keep a list of what I consider to be my seven modern embedded software principles.

And number three on the list is kiss the software, which is keep it simple, silly, or keep it simple, stupid, however you want to substitute it.

But every day when I go to write code, I go, all right, what are my principles I'm making sure I'm following? And That one is, like I said, it's in the top seven, top three.

Some other thoughts on things that you've learned that developers, even teams working with real-time operating systems might want to keep in mind?
Yeah, the, you know, so, so keep it simple, but, you know, in practical terms, you know, there's other things too, like function calls kill.
So, you know, if you have, you know, the more nested function calls you have, you know, each one of those eats up tons of performance, you know, pushing, pushing registers on the stack, return address on the stack, doing all that stuff and then popping it back off.
So keeping your function call nesting and the number of function calls down to a minimum is good too.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.