If you believe all the hype, it seems that AI is being integrated into nearly every embedded computing platform. It may not be everyone, but the percentage is fairly high and growing.

So, as a developer, do you know what your starting point should be for your project?

What Vin and I discovered, thanks to Avijit Sinha, Senior VP of Strategy and Global Business Development at Wind River, is that a whole lot of questions need to be answered before you even get to the starting point. Hear it for yourself on this episode of the DevTalk with Rich and Vin podcast.

You likely have heard of the Rust programming language, known for its safety features. But, like me, you may not know its details, and frankly, why you should be considering it for your next design. For those reasons, Rich and Vin invited Jonathan Pallant, a Senior Engineer with Ferrous Systems, to join them on this episode of DevTalk with Rich and Vin.

Just about everybody in the engineering space has reverse-engineered a product at some point. It might have been for professional reasons, like seeing how a competitor is attacking a problem or simply seeing how they engineered a product. Or it could have been for personal reasons, because the product stopped working, or simply because they wanted to.

Note: If you search for “Tear Down” on Embedded Computing Design, you can see the products we’ve reverse-engineered.

Then there are those people, like the folks at emproof, who get paid to reverse-engineer products, particularly on the software side. Tim Blazytko, the company’s Chief Scientist, Head of Engineering, and Co-Founder, joined us on this episode of DevTalk with Rich and Vin to share some of his experiences with reverse engineering.