The big lie about AI coding
A rant against what the host calls the "Markdown Industrial Complex" influencers packaging prompt files, "skills," and agent stacks as proprietary AI-coding methodology. His claim: there is no special skill in AI coding beyond picking a reasonable effort level and putting in long hours, and the people shipping huge volumes of PRs are just working 10-12 hour days. He argues the tricks people distribute are usually AI-generated themselves, address problems newer models already solved, and that real capability gains come from labs post-training the models, not from your prompt folder.
- The trend started with a widely-starred repo of Markdown files (referred to as "G stack," credited to Y Combinator's Gary Tan) that instruct an AI to act like a software engineer, CEO, etc. now imitated by many others, including Matt Pocock's "skills."
- The influencer who claimed 2,500 PRs shipped to production in a month did it by working 10-12 hours a day, not by using a secret workflow; the host says that volume is normal for full-time agent use.
- He cites Dax (opencode) on the core inversion: models improve faster than tinkerers, so elaborate custom setups usually solve problems that no longer exist, and someone naively using vanilla Codex is more likely to be on the state of the art.
- Token-saving "prompt of the day" optimizations may shave a tool call but won't change the big-O of your work and often waste tokens.
- He defends DHH for saying two frontier agents know Elixir better than he does, calling that an honest admission rather than an abdication of responsibility.
- Skills files are often generated by asking the model to write up whatever it just did and then redistributed "rain dances and superstition wrapped in a Markdown file"; the changelog prose itself reads as AI-written.
- What actually teaches agents to work like real engineers is lab post-training, not a skill file; a weak model won't be transformed by one.
- Beginners bookmark these repos assuming hidden utility, which inflates star counts and feeds the cycle his advice is to stop bookmarking and just prompt more and work harder.
This is the argumentative core of the video the clearest reason elaborate agent setups go stale, plus the meme contrast between stacked markdown files and professionals just opening a chat window.
A weird inversion with LLMs is the models improve faster than the tinkerers. When I see people with custom workflows and setups, they're all addressing problems that don't exist anymore. The person naively using vanilla codex is more likely to be experiencing state-of-the-art.
Defends DHH's "two frontier agents know Elixir better than me" position and then states the video's thesis in one line, including how skill files actually get made.
The only real skill in AI coding is knowing which effort level to use. Everything else is influencer propaganda... It's just rain dances and superstition wrapped in a markdown file.
Let me tell you how Lauren shipped 2,500 PRs to production. She worked 10 to 12 hours a day. That's it.
Anytime you get impressed that an agent did something, it's not because you prompted it in a special way. It's because the agents are just impressive now.
The thing that teaches agents how to work like real software engineers is the labs doing post-training on the models.