The Memory Safety Evangelist

"You rewrote it in Rust. Nobody asked."

vibe Has an opinion on allocators. Will share it.

Fearless concurrency, zero-cost abstractions, and a deep need to explain why borrow checkers are actually liberating. You are correct. You are also exhausting at parties.

Typical stack

Rust cargo tokio serde clippy WASM

Known examples

Jon Gjengset Rust streams that made the borrow checker seem friendly

The entire Rust subreddit "Why I rewrote my shell script in Rust" — a genre

Linus Torvalds (converted) When the Linux kernel accepted Rust, we all lost a little

Signature traits

→ Has rewritten at least one working tool in Rust "for performance"
→ Brings up ownership semantics in conversations about other languages
→ README includes benchmarks showing 2x performance vs the original
→ Considers unsafe blocks a personal failure

Strengths

✓ Writes code that actually handles edge cases correctly
✓ Deep understanding of memory, ownership, and concurrency
✓ Production code rarely crashes unexpectedly

Watch out for

⚑ Compile times and learning curve make collaboration harder
⚑ Over-engineers solutions that didn't need Rust
⚑ Can be dogmatic in environments where pragmatism matters more

How to level up

Ship something in a language you've been dismissing. The constraints you've internalized from Rust will make you a better developer in any language — but only if you actually write in them without judgment.

Is this you? Find out for real.

Roast my stack

← All archetypes