Articles are single-page pieces that give a whirlwind tour of a specific topic.
They're different from series, which go very in-depth, taking many detours.
I started experimenting with asynchronous Rust code back when
was all we had - before
async/await. I was a Rust baby then (I'm at least
a toddler now), so I quickly drowned in a sea of
Hey internet! So, someone broke into some of my accounts.
I'm taking entire responsibility for this - there's the part where I fucked up, and if I didn't fuck up, then none of this would've happened.
I've been banging the same drum for years: APIs must be carefully designed.
This statement doesn't resonate the same way with everyone. In order to really understand what I mean by "careful API design", one has to have experienced both ends of the spectrum.
In order to increase fluency in a programming language, one has to read a lot of it. But how can you read a lot of it if you don't know what it means?