Skip to content

Who to Learn From

The fastest way to get better is to watch people who are visibly good at it and steal their patterns. This is the watchlist behind the Pattern Library — ranked by practical signal density (concrete wisdom you can apply tomorrow).


NameWhereDistinctive contributionBest single piece
Simon Willisonsimonwillison.net · @simonwThe most prolific, reliably-practical chronicler of LLM toolingAgentic Coding
Armin Ronacherlucumr.pocoo.org · @mitsuhikoFlask creator → the most-cited agentic-coding methodologistAgentic Coding Recommendations
Geoffrey Huntleyghuntley.com · @GeoffreyHuntleyOriginator of the Ralph / agent-loop patternRalph Wiggum as a software engineer
Peter Steinbergersteipete.me · @steipeteCurates the field’s best “essential reading” roundupsJust Talk To It
Thorsten Ballregisterspill · @thorstenballDemystified agent internals for a generationHow to Build an Agent
NameWhereDistinctive contributionBest single piece
Shawn “swyx” Wanglatent.space · @swyxCoined “AI Engineer”; runs the field’s trend radarThe Rise of the AI Engineer
Mitchell Hashimotomitchellh.com · @mitchellh”Always have an agent doing something”; turn mistakes into lint rulesGhostty & His Agentic Workflow
Steve Yegge@Steve_YeggeBig-picture labor/skill-shift essaysRevenge of the Junior Developer
Hamel Husainhamel.dev · @HamelHusainThe definitive practical voice on LLM evals / error analysisYour AI Product Needs Evals
Boris Chernyhowborisusesclaudecode.com · @bchernyCreated Claude Code; the source on how it’s meant to be usedHow Boris Uses Claude Code
Cat Wu@_catwu”Delegate to it like an engineer, don’t pair-program”How Anthropic’s product team moves faster
Thariq Shihiparthariq.io · @trq212Best voice on general-agent (non-code) workflows + skillsClaude Code is All You Need

Sid Bidasaria (sidb.io) · Mario Zechner (@badlogicgames) · Jeremy Howard (@jeremyphoward, the llms.txt standard) · Orta Therox (@orta) · Kenton Varda (@KentonVarda) · Eric Provencher (@pvncher, Repo Prompt).


X has no feed, but almost everything else does. Make open feeds the backbone:

  • RSS / Atom — most of the blogs above publish a feed (Simon Willison’s atom/everything/, Armin’s feed.atom, Substacks via /feed). This is the highest-signal, most stable layer.
  • GitHub releases — append releases.atom to a repo URL to follow ships.
  • Hacker News — keyword feeds via hnrss.org (e.g. ?q=Claude+Code&points=50) catch posts even when you miss the blog.
  • Newsletters — Latent Space, Register Spill, Simon’s, Hamel’s.
  • X — build one list of the handles above; there’s no native feed, so this is the one surface that needs a scraper.