Robinson says he built a Rust image compressor that compiles to WebAssembly and a SvelteKit app without writing code by hand. He also used agents to create a Space Invaders clone in Verilog for an Analogue Pocket, despite having little experience with the hardware. Projects he would not have attempted a year earlier now feel achievable.
AI codes better than me. Now what?
Lee Robinson of Cursor discusses how coding agents are changing software engineering and how engineers can adapt; the page identifies the channel as leerob.
Robinson says current models are better at coding than he is and let him take on more ambitious work. He describes moving cursor.com from a CMS to Markdown and MDX in days, after expecting the migration might take weeks. As code gets easier to produce, he argues, the broader work of building software matters more.
Robinson expects models to become capable across most software engineering tasks, while arguing this does not mean software jobs will disappear. He recommends learning coding agents and using them to handle repetitive work such as boilerplate, JSON changes, and debugging shell errors. With code cheaper to produce, he says engineers should develop product judgment and build, market, and grow things people value.
Robinson cautions that relying too heavily on models can create the illusion of understanding. He suggests asking them questions like a patient pair programmer and using them to create guided mini-courses. For his recent projects, those lessons helped him learn Verilog, hardware abstraction layers, and compilation.
Robinson acknowledges that handing off code can feel like losing part of the craft. He says the goal was never code for its own sake, but building something worthwhile and being proud of it. He is optimistic about using AI to improve that work in 2026.
Takeaways
- Learn a coding agent by applying it to real work; fluency can help you take on more ambitious projects.
- Delegate repetitive coding and debugging so you can focus on decisions that shape the product.
- Practice the full product cycle: identify a need, build a solution, reach users, and learn from them.
- Use agents to teach unfamiliar topics, then check that you can explain the ideas yourself.
- Judge the work by what it enables people to do, not by how much code you wrote.
Mentioned in this talk
Search inside this talk
What was claimed 7
- uses
“work with coding agents to write Verilog code”
YouTube Unverified1 source· Talk
- feature
Cursor: AI features in its code editor
“Cursor was also doing a really good job on the AI features”
YouTube Unverified1 source· Talk
- featurelarge language models: Improved code generation, instruction-following, and tool-calling abilities
“they've gotten really good”
YouTube Unverified1 source· Talk
- feature
Cursor: Agent
“Cursor's agent had just come out”
YouTube Unverified1 source· Talk
- uses
“I actually moved cursor.com off of a CMS to just Markdown and MDX files”
YouTube Verified2 sources· Talk
- uses
“I did this entirely with coding agents”
YouTube Unverified1 source· Talk
- featureAI agents: Can help engineers handle drudge work and learn unfamiliar topics
“Use coding agents for that stuff”
YouTube Unverified1 source· Talk










