mcraealex16

Type state programming with embedded Rust has stopped me from a number of bugs so far. The important thing for me is that these bugs were caught at compile time which makes a world of difference in terms of productivity. The biggest pain point is how different the libraries for different microcontrollers are. I feel over time they will converge as things stabilize, time will tell.

I have found my rocketbook[0] extremely useful for the task. Its almost as good as real paper and you can find the pens anywhere. Only issue is once you scan it you can't edit it.

[0] https://getrocketbook.com/

Maybe it's just my experience, or lack of it, with cpp but everything feels hacky. With rust it just feels right. The websites like docs.rs and crates.io are amazing and there's no equal in cpp.

The issue I have with this is there isn't a consensus about what and if any of these products work. The IES (illumination engineering society) has released a couple articles about why consumers should be weary of products that claim to control the rythms and after attending a talk from the IES on the subject I'm not convinced any of it works (at least to the degree marketing says it does)

https://www.ies.org/fires/circadian-lighting-an-engineers-pe...

Will RISC-V have any effect on this? Is there a way to use RISC-V that solves at least some of these problems. It seems like it should be a priority to solve this no?