Code was our medium for thought
wattenberger.com · 1,073 words · saved by 8 readers
Code was not just the output—it was where we explored problems, made decisions, and figured out what we wanted.
What should we build? I'll build a beeswarm of Notable AI Models releases over time. First I'll pull the Epoch AI dataset details and inspect the existing chart patterns. Explored 2 files · 4 searches There's already a related release chart. I'll rebuild the opening around publication date and use Epoch's Notable AI Models CSV as the source of truth. Fetched notable_ai_models.csv Recent releases are dense, so I'll keep publication date exact on the x-axis and use vertical position only to pack overlapping marks. Ran collision-safe beeswarm layout I'll keep the result quiet: restrained…
saved by
- Katherine Huang
- abinaya dinesh
- Ratan Kaliani
- Emma Guo
- Nhật Nguyễn Thế
- Trevor Trinh
- Adani Abutto
- Yash Karthik
related reading
- Cognitive load is what mattersminds.md
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- claude code is not making your product betterethanding.substack.com
- Software Engineering in the Age of AIadiamond.me
- Writing Code vs. Shipping Code: Productivity Effects Across Generations of AI Coding Toolsmuratbuffalo.blogspot.com
- Don’t Outsource Your Thinkingteltam.github.io
- Thoughts on slowing the fuck downmariozechner.at
- Understanding is the new bottleneckgeoffreylitt.com
- How coding agents read your code (and how to write for them)modem.dev
- Thoughts on slowing the fuck downmariozechner.at
- Why write code in 2026softwaredoug.com
- Here’s how I use LLMs to help me write codesimonwillison.net