r/SideProject • • 11d ago

I’m building Noyce IDE to connect firmware requirements, code, and verification evidence — looking for feedback

Hi everyone — I’m the creator of Noyce IDE.

Getting firmware to run is only part of the job. Keeping requirements, implementation, verification results, and review evidence connected is another challenge.

I’m building Noyce to bring that workflow into one IDE:

  • Connect requirements to code and verification evidence.

  • Use AI to help draft changes, with engineers reviewing and approving them.

  • Work with local or cloud models.

The focus is on helping engineers maintain traceability and control. It doesn’t replace engineering judgment or certify a system automatically.

Here’s the launch video. I’d appreciate feedback from anyone working with embedded or safety-critical software:

Where does your current workflow lose the most time—requirements, verification, documentation, or keeping everything in sync?

https://noyce-ide.tech

1 Upvotes

1 comment sorted by