A few weeks ago I left Meta (prev. Facebook). In this post I reflect on my time there, especially projects and lessons learned. I’ll bias towards more recent projects because I remember them in more detail.
I always refrained from talking about my work projects on my blog to reduce the risk of any accidental leak, even though I always worked on internal tools and infrastructure, so nothing particularly confidential. Now I can be more open about the projects I worked on and link back to posts I wrote related to them during the time. This is a long post, detailing 14 years of work.
Tokio is a Rust library for writing and running asynchronous code. It was started by Carl Lerche, Alex Crichton, and Aaron Turon in 2017, interestingly even before Rust had the async / await syntax.
I plan to do a series of posts on Tokio. In the first installment, we provide an overview of Tokio, focusing on the user-facing semantics, covering enough detail so that it doesn’t feel like magic.
I’ve been using RSS on and off with Feedly but I often forget to check it. I have had more success with newsletters, where I receive posts directly in my email. A recent example is Philip Su’s Molochinations which uses Substack, which offers newsletters out of the box.
I don’t use Substack and didn’t want to pay for a service to add this feature, so decided to explore creating one from scratch, using AWS infra. In this meta post, I’ll describe a serverless architecture that implements this.
In The Pleasure of Finding Things, Richard Feynman recounts a childhood event in which a boy comes to him and asks “See that bird, what kind of bird is that?” and Feynman concedes he has no idea, and the boy proudly answers himself “It’s a brown-throated thrush” and that “Your (Feynman) father doesn’t tell you anything”.
Feynman pointed out that the boy knew about the name of the bird but did not know anything else about it and used it to illustrate shallow knowledge. Later in life he even joked that this attitude caused him trouble because he often didn’t know the conventional names for effects in physics, but understood them once someone described what the effect actually was.
Despite this argument against names, in this post I’d actually like to share some reasons on I think names can be beneficial.
For most operating systems, when memory usage grows beyond what the hardware can support, the kernel starts swapping, i.e. moving data from memory to disk. In this post, we’ll study how the Linux kernel does this, as part of the more general memory reclamation process. We’ll also cover the memory allocation flow, because memory reclamation is just one part of it, one of the unhappy paths.
First, we’ll go over the different components involved, and then how they fit together in the memory allocation flow and then memory reclamation via swap and zswap.
Visit archive to see all posts...