Zachary Pierce

At @AuxonCorp we regularly end up bumping into rough edges around using #rustlang for embedded development. @ZackTheEngineer leaned into the abyss and came out the other side with something useful to give back to the community.

@wilcoxjay @johnregehr @mycoliza That might have been a secret subtitle to the talk. "Have you considered throwing generative input at your problem?"

cool reasons to care about program verification #COGoldRust

@johnregehr @mycoliza Happily, the focus was on empirical verification rather than formal verification, so I was able to skip over that aspect without much guilt.

I'm going to take to heart the feedback from my talk at @COGoldRust and see if I can develop some useful insights on the measurable efficacy of coverage-guided property-based testing in Rust.

Verifying myself: I am zacharypierce on Keybase.io. a1Swrp7zLVsEztdyYfQnt6vfvJ-cmgOmKJiy / keybase.io/zacharypierce/…

@gcouprie The benchmarks are kind of like a cake bake-off, and nom is a tasty brand of flour. Great stuff, but we're really comparing recipes right about now.

Check out our latest white paper, "Safety Implications of Serialization Timing in Autonomous Vehicles," by @ZackTheEngineer and @gen_nja news.ycombinator.com/item?id=156570…

@gen_nja @clearydude @ZackPierce Hey, I got an account. Also, thanks!

I wrote a blog about neat testing stuff! polysync.io/blog/how-i-lea…

We've said it before,we'll say it again. @rustlang could revolutionize safety, concurrency, security of embedded sys polysync.io/blog/session-t…

Interesting blog about @rustlang and SBE (Simple Binary Encoding). polysync.io/blog/session-t…