Barr Code
Michael Barr, an internationally recognized expert on embedded computer design, writes about firmware architecture and development processes that help keep bugs out of embedded systems.
Archives
-
Trends in embedded software design
As the magazine that catered to embedded systems programmers closes, the future lies in less... Read More
-
Building reliable and secure embedded systems
Neither reliability nor security can be tested, debugged, or patched into a product. They must be... Read More
-
Combining C's volatile and const keywords
Does it ever make sense to declare a variable in C or C++ as both volatile (in other words,... Read More
-
Firmware forensics: best practices in embedded software source-code discovery
Remember unintended acceleration? Here's what NASA should have examined in Toyota's software. Read More
-
Five dangerous coding standard rules
Don't follow these five dangerous coding standard rules… TODO. Read More
-
How to enforce coding standards automatically
Coding standards are an important tool for fighting bugs. Unfortunately, too many well-intentioned... Read More
-
What belongs in a header file
What sorts of things should you (or should you not) put in a C language .h header file? When should... Read More
-
Unintended acceleration and other embedded software bugs
Despite the redactions, we can still learn some interesting facts about Toyota's embedded software... Read More
-
Social networking for engineers
Not all engineers hate Twitter. Many use social media site wisely. Michael Barr, a former editor in... Read More
-
Five more top causes of nasty embedded software bugs
What do memory leaks, deadlocks, and priority inversions have in common? They’re all Hall of Famers... Read More


