Software in London. Trying to make things go faster.

Joined July 2009
23 Photos and videos
Pinned Tweet
New post: I added Direct I/O support to Cassandra for compaction reads, cutting p99 read latency by 5x (and p50 a little). Walks through the page cache mechanics, benchmarking, and when to enable it. Some funky charts along the way. lightfoot.dev/direct-i-o-for…
1
5
58,029
Sam Lightfoot retweeted
If you're interested in SSD internals and how to use them efficiently, our paper, “How to Write to SSDs,” has been accepted to VLDB and is currently on the Hacker News front page. vldb.org/pvldb/vol19/p1469-l…

13
112
796
52,700
An excellent take
During my time at @awscloud I tried to be an astute observer of how the Senior Principal and Distinguished Engineers carried themselves in new projects/teams and design reviews. This has made a lasting impact on how I operate as well as evaluate others. All of these "Very Senior" engineers are smart but the absolute best ones were humble, secure, incredibly curious, and appreciated the history and path of a system. They can jump into whole new domains and immediately win over the people under them that ultimately do the work. The worst Very Senior engineers show up and inflict their insecurity by asking divisive and superficial questions like "why didn't you use {{language foo}} or {{database bar}} or {{platform qux}}?" These very questions reveal their inner fear: they don't have the depth and breadth their position requires.
71
Sam Lightfoot retweeted
As a manager, it took me far too long to learn that meetings aren't actual work. I thought meetings drove output. Turns out, most meetings are about control, not collaboration. About signaling ambition versus pursuing it. If you can't pass these three tests, cancel the meeting:
22
70
1,054
197,588
Sam Lightfoot retweeted
Feb 23
Someone really built this. A VS Code extension that turns your AI agents into pixel art characters working inside a virtual office.
224
702
10,708
1,014,091
Sam Lightfoot retweeted
New Engineering blog: We tasked Opus 4.6 using agent teams to build a C compiler. Then we (mostly) walked away. Two weeks later, it worked on the Linux kernel. Here's what it taught us about the future of autonomous software development. Read more: anthropic.com/engineering/bu…
855
2,493
21,256
8,515,229
Linus vibing. Things I did not expect.
10 days into 2026: - Terence Tao announces GPT & Aristotle solve Erdős problem autonomously - Linus Torvalds concedes vibe coding is better than hand-coding for his non-kernel project - DHH walks back “AI can’t code” from Lex podcast 6 months later An acceleration is coming the likes of which humanity has never experienced before
90
Sam Lightfoot retweeted
The Path of a Packet Through the Linux Kernel net.in.tum.de/fileadmin/TUM/…
9
241
1,366
230,588
Sam Lightfoot retweeted
20 Nov 2025
Replying to @BenjDicken
Tales of the Tail is one of my all time favorites research.google/pubs/tales-o…
1
2
24
1,600
An excerpt from the OSTEP book regarding distributed file systems. Sounds familiar - is it just scalability the protocol affects @jorandirkgreef? :-) youtube.com/watch?v=yKgfk8lT…
39
TIL: The Chrony NTP daemon fixes clock drift fast — slew rate of 100,000 ppm vs ntpd’s 500 ppm. Sparked by the 'Order and Time' chapter from @DominikTornow's Distributed Systems book.
2
108
Sam Lightfoot retweeted
It still has to be reviewed, but finally the cursor based C* compaction patch is in the open: issues.apache.org/jira/brows… "3-5x faster [compaction] in most scenarios and allocates ~20mb vs. multiple GB[per compaction]" :-)

1
3
7
1,522
Sam Lightfoot retweeted
How to develop taste: Step 1: Ignore all the hustle-culture get-rich-quick BS. If someone isn't motivated by quality they won't develop it. Step 2: The essence of taste is simplicity. Simplicity is hard. Any time a system is getting messy or complicated ask yourself "how could we have designed this differently to make it more simple?" Step 3: Never dismiss a decision you don't agree with as someone being an idiot. They had a reason for making that decision and by learning what it was you'll learn perspective plus more about how humans think and use systems. Step 4: Good taste doesn't show up on short timescales. You won't know if a decision was good until years of usage and changing requirements. If you hop between jobs too fast or don't own projects long enough you won't learn this. Step 5: Never be satisfied with any work you do. This isn't a recipe for happiness but it's a recipe for introspecting every day on what could have been better. Good taste evolves from a constant desire to build things that solve real problems in the most elegant way possible. Step 6: You can't derive taste from data-driven decision making. You need to make decisions based on intuition. Develop the confidence to make your own decisions, stand behind them, and learn when they could have been better. Step 7: You also won't learn good taste from an LLM. LLMs traffic in competency. Taste is about excellence. This one is on you. Step 8: There is no step 8, you've just got to try really hard every day, ignore most of what you read on the internet, and get slowly slowly better over time.
16 Sep 2025
Replying to @jamesacowling
how do i develop taste dude
31
80
889
77,758
Sam Lightfoot retweeted
Replying to @penberg
Or we can do better: To hedge physical requests for consistency and tail tolerance, and with logical availability rather than CAP’s reduced definition of physical availability. Plus, tighter P100s on latency than what CAP would give. TB recently started hedging for all these reasons.
2
5
20
2,913