Software Engineer (Storage) @supabase. Creator of pypacktrends.com. Co-organizer of madisonsystems.xyz. Peeling back the layers of abstraction.

Joined March 2012
445 Photos and videos
David will not rest until people realize it's Aspire not .NET Aspire
Replying to @G__HaC
Aspire, not .NET Aspire
2
198
This is the paper that inspired me to get into systems programming
1
1
205
Tyler Hillery retweeted
Jun 3
. @supabase is the newest sponsor for mise/en.dev! thanks so much! en.dev/sponsors.html

5
69
2,557
I'd love to rack and stack a server in a DC someday
Bringing up new Tigris racks online soon for your fast storage needs!
5
301
2 months on Math Academy and I've made it to Diamond League
2 weeks in and I'm really enjoying Math Academy so far
1
1
148
Tyler Hillery retweeted
I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem. As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)! I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work. It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results? 88ms => 1.5ms 150K allocs => ~500 allocs Incredible right? Nope. My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path. This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput. The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity. Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.
308
979
8,938
791,177
Finally pulled the trigger on a kindle and I absolutely love it. Should have gotten one ages ago
1
11
266
Another great Madison Systems paper discussion!
Reminder, Madison Systems is having another paper discussion in 2 weeks. This time, we'll be discussing: Scalability! But at what COST?
1
4
375
Form was sloppy but finally hit the 405 deadlift
3
9
656
This is the way. It's Saturday 7:20am and I've already finished my daily Math Academy goal.
If your excuses keep postponing your training, do it first thing in the morning before your excuses finish loading.
2
165
I really like @ReadwiseReader's chat feature to quickly ask questions about a passage
1
8
832
3 more days, get to reading!
Reminder, Madison Systems is having another paper discussion in 2 weeks. This time, we'll be discussing: Scalability! But at what COST?
1
2
640
Tyler Hillery retweeted
In the long run, the world rewards quality. In the short run, keep that in mind. Do the harder thing today to make tomorrow easier.
5
24
263
6,932
I'm very impressed by the digital electronics and computer architecture course by @pikuma. Great educator.
6
17
307
12,906
Tyler Hillery retweeted
Great take. The issues causing Bun to switch to Rust have much to do with Bun than Zig. People give languages too much credit. You can write wonderful or terrible software in any language!
My take on the bun stuff lobste.rs/s/lapqbz/bun_s_rus…
2
1
5
682
Building a computer from first principals
1
8
283
Reminder, Madison Systems is having another paper discussion in 2 weeks. This time, we'll be discussing: Scalability! But at what COST?
1
11
1,533