Joined April 2026
27 Photos and videos
Pinned Tweet
SEO tools answer the wrong Q. They tell you what happened. They don't tell you what to do. SERP Refresh analyzes AI Overviews, competitors, and your content while you're searching, and gives a clear recommendation: Refresh, merge, or write new. serp-refresh.leestack.dev
3
51
My first shot using telephoto lens! šŸæļø
5
David Lee retweeted
Programming is understanding. If you don't understand what you are doing, you are not programming. You are generating text.
228
1,622
14,258
428,445
David Lee retweeted
Replying to @geerlingguy
It's kinda wild that all the janky workarounds to avoid address exhaustion are less buggy than an implementation of a standard.
9
9
890
44,043
Most Golang dev still don’t get: goroutines are a runtime abstraction. They own stacks, but they are not stacks. Their metadata lives on the heap, while their stacks hold the active execution state of the goroutine.
1
1
18
I should just say: a goroutine is a runtime object that owns a stack.
12
9 Years of Camera Setting Knowledge in 29 Minutes youtu.be/vu5ohljtB-A?si=aCh7…

10
Everyone is obsessed with reasoning benchmarks. But reading the DeepSeek V4 technical report, the takeaway for me was the opposite: Gemini 3.1 Pro still appears to have the strongest world knowledge among mainstream models. You can’t reason about facts you don’t know.
10
We are rapidly approaching a world where nobody wrote the code and everybody owns the outage.
1
1
23
ā€œMove fast and break thingsā€ has evolved into ā€œPrompt fast and deploy things.ā€
10
If you secretly install Codex on someone’s computer and connect it to your phone, you’ve basically created an AI-powered RAT.
20
A better version could be: the better engineers are at preventing problems, the harder it is for others to see the value they create. How do you reward mistakes not occurring?
Good software is invisible. That's why all software is bad because the managers demand visibility of programmers work.
1
34
5 million Codex users sounds huge until you compare it to ChatGPT’s ~900 million users. We’re not early to AI, we’re early to using AI well. Most people are still asking questions. A small minority is already building coworkers.
1
2
31
I don’t know what’s happening with ChatGPT recently. I ask about cameras, it recommends restaurants. The context window is open, but the packets are clearly being routed somewhere else.@OpenAI
1
33
ByteDance built an entire business around charging for the Export button. Codex treated CapCut like a slow API and pressed it for me.
2
144
Pretty good review for Opus 4.8, @OpenAI please stay put where you are, you are already a winner!
3
112
Wow, this is really heavy! @Wealthsimple
28
I write intensively on cases like this in leestack.dev yes, I use AI, the same with how I use Internet to search to replace those Linux books references workflow, I monitor, I understand and I verify with good system thinking!

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.
1
54