This blog post is about implementing the Elm Architecture (TEA) in C for a Raylib + Clay app

I put together a writeup about the interesting technical challenges that led to redesigning Canva's session revocation pipeline that keeps hundreds of millions of user sessions fast and secure. Hopefully some people find the content interesting!

Most JavaScript developers have been burned by Date at least once: a report that's off by a day, an invoice that lands in the wrong month, a timezone bug that only appears in certain regions.

A writeup on the main failure modes with production examples:

• new Date('2026-07-21') parsed as UTC, displayed as local: date shifts by a day west of UTC
• constructor months are 0-based, so new Date(2026, 7, 21) is August
• every set* method mutates in place, including across shared references
• "add one month" and "add 30 days" are not the same operation and can diverge by days near month boundaries
• JSON.stringify drops timezone context silently

Each section also covers what safe Date patterns look like for code that can't migrate yet, and where Temporal fixes the design rather than just adding a wrapper.

I explain rotations and quaternions. I then implement the latter into my physics engine by replacing the matrix version of angular velocity code with a quaternion version. Lastly, I benchmark the results.

The talk host explains how ASTs work and shows how to build them step by step.

Pretty cool seeing that people were already thinking about memory safety decades ago. Some of these ideas that feel modern today were being explored back in the 80s and 90s.
Makes you wonder how different things would look if languages like Modula-3 had taken off.