Dyad Studio: Engineering Products of the Future

In the world of product engineering, it can feel like a war zone where hardware design and software engineering are locked in a battle to control the future of product development. Where hardware engineers want to prototype hardware, run physical tests and use model based approaches while software wants to write code, run unit/integration tests, automate with CI and generally fail faster. Where manufacturing wants final blueprints so they can prepare the dies and tooling while software engineers are still working on the final version of the operating system which they will push out with a patch just before the product reaches the customer. Where functional safety wants determinism and auditability while software wants to incorporate the latest AI and machine learning technologies.

But this isn't a war. The reality is that hardware and software are both part of the equation and "software defined" doesn't mean "hardware free". Ironically, both sides want the same thing. If you look closely, the fundamental issues really aren't about the people, it is about their tools. If each group uses tools that consider only the needs of one group, it isn't surprising that other groups use other tools. Now this might make it sound like the solution would be to seek an "Enterprise solution". But those tools are too often bloated, opinionated and very slow to innovate. As such, neither side wants to use them.

We believe the way forward is processes built around loosely coupled tools that recognize that they are simply one step in a larger process. This is why we are building the Dyad Platform. Today, we are launching the first building block in the Dyad Platform, Dyad Studio, a Visual Studio Code extension for modeling, simulation and analysis.

Download Dyad Studio here: https://marketplace.visualstudio.com/...

Documentation: https://help.juliahub.com/dyad/dev/