Happy I had the chance to sit down with @EclipseFdn to talk about Eclipse uProtocol, our open-source Software Defined Vehicle communications framework. Link to interview below 🚗💨

RT @__phantomderp: Thanks to Steve Downey and others, optional<T&> officially adopted into C++26. It would've been great during C++17, but….

Join millions who have switched to Grok.

Working with @jfbastien for the last half a year has been a highlight of my career! If you tick these boxes send him an email 📨.

RT @VicVijayakumar: productivity after kids is like ballmer’s peak. 1 kid: omg how do I get any work done when all I want to do is stare a….

RT @pants:

RT @kianamaiart: huge

RT @ahmadaccino: @C8Luna of course not, i use mspaint

But, retrofitting these things into a spec and language after the fact have proven to be fairly time consuming from what I've seen. And lead to "non-safe" defaults.

No shade on C++! It began under different circumstances, in a different time, and has had many great gradual improvements to improve its qualities for safety-critical. 🫡.

Ferrocene, the Rust safety-qualified compiler for Automotive, Aerospace, and Medical 👇 .

Not trying to minimize Ferrocene! Took real work. But gosh Rust sure had a nicer starting point with a commitment to memory-safety, thread-safety, and type-safety from jump.

Safety-Critical Qualification in Rust vs C++. Which is which, ya think? 🤔

RT @annalaura_art: woken up by sunbeams (1/2)

My life got a lot easier professionally when I realized my strength was not being the smartest person, but the person that's least willing to give up. ✌.

Have to know when to make a bet and when not to. Have to know when it suffices to write in a doc "yeah, we'll just solve that in way X" and when to know you should run a small PoC before writing checks you can't cash. Write "high impact" PoC code only for derisk or wow reasons.

Course, risk with these things abound. Nobody asked me to do any of this stuff, so egg on my face if it doesn't work out.

This was ehhhhh, 80% of my time over the last month spent not actively coding or designing, but instead spent trying to understand the pain points of the business and how I could use what I knew to improve things.

based on feedback from architect put together a "normalizing [Technology] roadmap" document (again ~15 pages), solicit feedback on roadmap document and get great additions from advanced and close to production folks.

presentation to director with team lead on plans (made four, various pros/cons) and picked one (i.e. got greenlight for Q1 2025 [Technology] PoC), wrote up two day PoC (some code here again) to prove in-theory production integration should work,.

started a [Technology] Watercooler Chat to make a casual place to continue to normalize it, began aligning with team lead on feasibility doc gathered feedback far and wide, one-week long PoC (actual code happened here) to confirm no blockers,.

The "things" I've done over the past month or so are: feasibility study (~15 page doc, lots of footwork), presentation to team to socialize a [Technology], schedule many 1-on-1's with peers and those in leadership to understand org structure and technology pain points,.