Rust's Concurrency Rule Doesn't Relax — It Moves
Rust's rule against shared mutable state doesn't relax once you add threads. It just changes who enforces it — and gains a second rule deciding who's allowed to cross the thread boundary at all.
Software Engineer · Stockholm · DigitalRoute
Engineering software, and rethinking how it's built in the age of AI. I care about systems that are fast, correct, and a pleasure to use — and about what changes when AI becomes part of how we build them.
| ALSO | Content creator · writer |
|---|---|
| FOCUS | AI systems · distributed systems |
Building Usage Data solutions at DigitalRoute
Going deep on Generative AI, ML & distributed systems
Learning Go and Rust for efficient, scalable systems
Writing essays and recording Udemy courses
Rust's rule against shared mutable state doesn't relax once you add threads. It just changes who enforces it — and gains a second rule deciding who's allowed to cross the thread boundary at all.
Why a GPU is architected nothing like a CPU, and the one ratio — arithmetic intensity — that tells you whether your code will ever be fast on either.
You type SELECT and rows come back. In between is a stack of twelve layers, each solving one very sensible problem. Here's the whole journey, following a single query from your terminal to the disk and back.
Open to conversations about engineering, AI systems, collaboration — or just connecting with fellow developers.