Making Embedded Systems: Design Patterns for Great Software

Excellent book. Detailed and well written

This book reads a little bit like a guided museum tour that walks you around a whole career. You'll get a sense of what sort of technical problems are out there along with generally applicable problem solving strategies to match. There's some diagrams for digging in on bite sized examples, and the more complex embedded problems are acknowledged with references to other specific-purpose guides. The strong narrative voice tying it all together makes it pretty enjoyable to read as far as technical books go.I had bought the first edition of the book to bridge the gap between my college degree and first embedded job, and I bought the second edition for the updates on how the industry has changed in the ~10 years in between editions. Its still the best embedded book I've read, and I'd still recommend it to my coworkers.

If:1.) You are an embedded engineer2.) You want to be an embedded engineer3.) You work with embedded engineers4.) You are interested in what embedded engineers doBuy this book. It is approachable and applicable to any and all projects an embedded engineer would be involved in. For the most experience to a someone interested in digging into a new discipline (you will need a basic engineering background however), get this book. One of my new favorite references to have in the office next to me (:Thanks Elecia!

Really great stuff that helped me a lot as a professional embedded firmware engineer to write better code. There were immediately valuable exercises that helped to understand my existing code base and refactor it into a more maintainable code base.

I really like this book. It sets out to provide an intro to the embedded space with more focus on software than hardware, but it has enough depth that it isn't just an intro book. The humor is great too, not so much that it distracts from the content but enough to lighten up the material and lower the activation energy needed to work through the book. What other book has a datasheet for a triceratops or explains interrupts based on a chicken pushing a button?I read the 1st edition as well, and the new edition has enough new content to justify upgrading. There is a lot of new material in this version that wasn't in the last.

Elecia White's latest book looks nice! Clearly this was written (and updated) by someone who understands embedded systems well and has seen a lot of stuff go down on real-world projects.Highly recommended for those looking to up their skills coming from pure software backgrounds, or domain experts who are looking for a more systematic way of making sure they have considered all the different aspects of embedded systems. Finally, this should be required reading for makers who are looking to go past the copy-and-paste-the-code-to-make-the-light-blink stage. And some fun pictures and examples as well.

I took Elecia's class a year or so ago. I've been writing code since the very early 80s - starting from 8-bit assembly (1802, 6502), to 68000 assembly, to C, then C++ ... these days it's mostly Swift / Kotlin, though embedded C / C++ / Rust is still my preferred space to play in. Anyway, I _still_ learned quite a bit from Elecia's class and 1st edition of this book. Some of it was stuff I knew way back then but hadn't used in a long time (memory-mapped I/O, interrupts, DMA), but a significant percentage was new to me. I cannot recommend her books enough.

A must have for every embedded software engineer, especially for beginners/intermediate.

Very well written - even with ober a decade of experience I enjoyed reading the book. Very warmly recommended.

This is an almost complete overview of topics to consider and learn for a career in Embedded Systems. Has a friendly voice, good humour and very easy to read. I have written up a comprehensive review under the title of "Making Embedded Systems - A Reader's Review" on my blog.

Great content and well written, but the book quality is terrible.. I am not even half way through it and it's loosing pages like a tree in autumn. Much better to just get the pdf.

Ich habe das Buch bis Kapitel 5 gelesen. Bis jetzt hat mir das Buch gefallen. Ich habe selbst 3 Jahre Erfahrung mit Embedded Systems. Dieses Buch ist nicht wirklich ein Fachbuch, bei dem man je nach Thema von Kapitel zu Kapitel springen kann. Die Autorin hat das Buch so interpretiert, dass sie den Designprozess wie eine Geschichte erzählt. Sie führt den Leser durch ihre Geschichte. Sie hat einige gute Design Patterns für die Softwareentwicklung im Buch grob erzählt. Das hat für mich einige Highlights gebracht, da ich vorher keine Design Patterns in der Entwicklung verfolgt habe. Das hat mich dazu gebracht, mehr Bücher über Design Patterns zu kaufen. Ich mag solche Inputs. Die Autorin hat auch einige Bücher im Buch empfohlen. Ich werde mehr berichten, wenn ich das Buch zum Ende durchlese.