Michael Caisse
@michael.caisse.io
bithead : C++, embedded, hardware, software, and mentoring. Passionate about Software Engineering. @intel Silicon Engineering. Sabre fencer.
The text and video don't match.
October 14, 2025 at 7:22 AM
The text and video don't match.
Slides for my cppcon-2025 talk on groov are here: michael.caisse.io/talks/2025-c...
Source code for demo is here: github.com/caisselabs/s...
Source code for demo is here: github.com/caisselabs/s...
October 10, 2025 at 2:01 PM
Slides for my cppcon-2025 talk on groov are here: michael.caisse.io/talks/2025-c...
Source code for demo is here: github.com/caisselabs/s...
Source code for demo is here: github.com/caisselabs/s...
I just gave a more in-depth talk at cppcon 2025 on groov. The source for the 2024 talk is available here: github.com/caisselabs/s...
It probably should be updated with the latest releases of groov and senders. I'm cleaning up the repo for my cppcon 2025 talk and will link it here when it is up.
It probably should be updated with the latest releases of groov and senders. I'm cleaning up the repo for my cppcon 2025 talk and will link it here when it is up.
GitHub - caisselabs/stm32-senders-blinky
Contribute to caisselabs/stm32-senders-blinky development by creating an account on GitHub.
github.com
October 4, 2025 at 1:21 PM
I just gave a more in-depth talk at cppcon 2025 on groov. The source for the 2024 talk is available here: github.com/caisselabs/s...
It probably should be updated with the latest releases of groov and senders. I'm cleaning up the repo for my cppcon 2025 talk and will link it here when it is up.
It probably should be updated with the latest releases of groov and senders. I'm cleaning up the repo for my cppcon 2025 talk and will link it here when it is up.
From my cppcon 2025 talk?
October 4, 2025 at 1:00 PM
From my cppcon 2025 talk?
Sorry to see this. )o:
September 30, 2025 at 3:51 AM
Sorry to see this. )o:
Oh! I love the look. Now I'm interested.
August 19, 2025 at 11:37 PM
Oh! I love the look. Now I'm interested.
Named by an iso committee member
August 6, 2025 at 2:43 AM
Named by an iso committee member
I'm failing to find the perfect JF style punny answer. They are appropriate when your concurrency implementation is easily cooperative. Unfortunately, in c++ they are infectious so that everything in the stack using a coroutine needs to be/handle coroutines. I'm not a fan of intrusive solutions.
August 4, 2025 at 3:02 PM
I'm failing to find the perfect JF style punny answer. They are appropriate when your concurrency implementation is easily cooperative. Unfortunately, in c++ they are infectious so that everything in the stack using a coroutine needs to be/handle coroutines. I'm not a fan of intrusive solutions.