Better Embedded Systems - Key Takeaways

Dates Read: 04/25/2026 - 04/28/2026

Rating: 3/5

I picked this book up at work, and it did not disappoint. It's a straightforward read and, similar to its philosophy on modular code, each chapter is able to be read as a standalone chapter.

I really appreciated that because I wanted to read some chapters more than others, such as the requirements chapters, since I was currently in the process of developing my own requirements for a project and reviewing the existing ones for our codebase.

Prior to that chapter, I was unsure what a Change Control Board (CCB) was for, but now it's clear why I hear that term so often in our day-to-day discussions. Every change we make requires some form of validation and peer review, which is best done with subject matter experts on the CCB.

I will say, though, the chapter that was toughest for me to digest was the one pertaining to scheduling algorithms. Not because it was unclear, but because the concepts demand a lot of attention and focus to understand. Frankly, it was one of the better chapters for getting my hands dirty with more RTOS concepts, especially around multiple priority queues and interrupt architectures.

The flowcharting and diagram examples were also quite helpful. Wherever you go, it's often easiest to explain something to someone using a picture.

I had learned about many of these concepts in school, but it's great to reinforce them and remind myself not to get cocky or think I'm above the fundamentals. Flowchart before touching software or hardware.

The last thing I'll take away from this book is that it's not really meant to be read front to back. Instead, it's a reference book meant for you to jump to any chapter and skim to the parts you believe will help you solve whatever challenge you're facing that day.