Hi! I'm Amos. I write about how computers work - or at least, how
they sometimes work. I write long pieces in a casual style, where we take
our time to explore a problem. I tend to cover Rust a lot.
In my view, there's nothing that can't be explained if you're creative about
it. And I enjoy doing that very much! I've made long series about reading
files, the ICMP protocol, and I'm currently spending way too long talking about ELF executables.
Support me on Patreon,
in exchange for my eternal gratitude, and/or early access.
Technology, as seen on TV
Go to series overview
Enhance! In this series, we're looking at TV depictions of technology, and
reviewing how realistic they are. Of course, they're very rarely accurate,
but it's still interesting to take a look and try to figure out what they
could've been thinking of, and just reminisce in general.
More series are listed over there
What's in a Rainbow table?
In Veronica Mars and password hashes,
from my new Tech As Seen On TV series, we've
explored "cracking passwords" using brute-force methods, and then using
rainbow tables, which was much, much faster.
So you want to live-reload Rust
Good morning! It is still 2020, and the world is literally on fire, so I guess we could all use a distraction.
This article continues the tradition of me getting shamelessly
nerd-sniped - once by Pascal about small strings,
then again by a twitch viewer about Rust enum sizes.
Peeking inside a Rust enum
During a recent Rust Q&A Session on my twitch
channel, someone asked a question that
seemed simple: why are small string types, like
the same size as
String, but small vec types, like
SmallVec, are larger
There's more articles over there