Congratulations - That’s wonderful news 👏🎉

+1. One of the best such "other changes" I know is to decouple relentlessly (and perhaps recursively). Teams, code, schedules, ...

… including for relatively fringe PLs, in my experience.

A wonderful and inspiring lecture. Thank you!

Yes, so much of this. Glad I'm not alone in prompting my way through 'Don't apply a "fix" before you can explain the root cause.' Local flavor of what you describe: process hangs during shutdown -> no worries, wrapping a hard kill around it after a timeout - tada 😚. "Root cause before fix" pleease!

That’s such a cool project 👏

Roger that and yes, please do your utmost ;-)

Love your bite-sized Racket macro examples. Thank you! Q: What’s the most Racket idiomatic way to wrap/intercept the reads too (ignoring, as you said, that it’ll make things utterly unusable)?

Thank you for sharing!

Especially the trend of not publishing the raw "wire" protocol in favor of adoption-focused overweight SDKs has irked me for years ... +1 for "... It cuts down the amount of the API I need to learn upfront, and it cuts down how much future programmers (myself) reading the code need to understand."

🤝 100% matches my experience, and I find your take and outlook exciting!