Embedded Software Creation II - European Normative & Legislation
In this post I will explain the European Normative. I will answer the main questions and I will be open to answer all the doubts any of you could have. Please leave a comment and I will answer if i could.
Why I need to look and accomplish some standards?The main reason is if you want to comercialize the product in the European Union, if exists any European Directive that cover the product, the product must be marked with the CE mark. For USA it work in the same way by the...
Complexity in Consumer Electronics Considered Harmful
Jason Sachs watched his grandmother struggle with a Vizio TV remote, and it highlights a recurring usability failure in consumer electronics. He argues that small type, unclear icons, and modal controls make everyday tasks needlessly hard. The takeaway for embedded engineers is to prioritize common actions, separate advanced features, and design for low-vision and limited-memory users to avoid frustration and returns.
Requirements, Specifications and Tests
A practical workflow keeps embedded projects predictable and reduces late surprises. Start with a client-driven Set of Requirements, then derive a QA Test Set from those requirements, and write a Technical Spec that maps to the design. The method enforces change control, helps catch feature creep early, and makes final acceptance straightforward for non-engineer testers.
Embedded Software Creation II - European Normative & Legislation
In this post I will explain the European Normative. I will answer the main questions and I will be open to answer all the doubts any of you could have. Please leave a comment and I will answer if i could.
Why I need to look and accomplish some standards?The main reason is if you want to comercialize the product in the European Union, if exists any European Directive that cover the product, the product must be marked with the CE mark. For USA it work in the same way by the...
Requirements, Specifications and Tests
A practical workflow keeps embedded projects predictable and reduces late surprises. Start with a client-driven Set of Requirements, then derive a QA Test Set from those requirements, and write a Technical Spec that maps to the design. The method enforces change control, helps catch feature creep early, and makes final acceptance straightforward for non-engineer testers.
Always-On Intelligence Without the Cloud: Why it matters more than you think
Much of the AI conversation today is still focused on scale: larger models, more data, more compute. Embedded systems live in a different reality, where constraints are unavoidable, and efficiency is the priority. What’s emerging is not a smaller version of cloud AI, but a different approach altogether, the one that values locality, predictability, resilience, and trust. Always-on intelligence without the cloud isn’t just a technical milestone. It’s a change in how we think about where intelligence belongs.
