En 30 segundos
Nat Eliason builds a blog-to-social-post prototype with Cursor, works through errors and explains how he uses AI feedback when editing fiction. The episode is sponsored by Vanta.
- 1Debug the environmentCheck dependencies, paths and the commands actually running.
- 2Protect credentialsExclude secret files from version control and rotate exposed keys.
- 3Prefill is not publishingThe demo opens a composed post; it does not send it automatically.
- 4AI as an editorUse feedback to spot possible issues, then make the creative decisions yourself.
Conclusiones
- Start with a small, explicit application goal.
- Inspect errors, working directories and server processes.
- Keep API keys out of source control and client-side code.
- Use AI writing feedback as input to human editorial judgment.
- Treat labor-market predictions as forecasts, not facts.
Lee el texto editado por capítulos
Building the application
Scope, setup and the first generated code.
Nat Eliason demonstrates building a blog-to-social-post tool with Cursor, then discusses using AI to edit his science-fiction novel. This episode is sponsored by Vanta.
He starts with a small goal: paste a blog post, call an AI API and produce several short posts. Cursor’s agent generates a React-based project and supporting code from the request.
The episode includes a Vanta sponsorship. The initial setup stalls, so Eliason interrupts it, inspects the command and retries. He says a short written plan can help more complex projects stay focused.
Debugging and security
Resolve environment and server errors while protecting keys.
The demo exposes practical obstacles: package installation, dependency versions, nested project folders and commands run from the wrong directory. Reading errors and isolating steps help narrow the problem.
Cursor’s automatic command mode can execute commands without individual approval. Eliason leaves it off in the demonstration; review generated commands and use controls appropriate to the environment.
The generated application uses a server to call the AI API. The first attempt fails because the frontend and server are not both running, followed by a response-format error.
The speakers discuss putting the API key in an environment file instead of source code. An environment file is not automatically protected: keep it out of version control, keep secrets server-side and rotate any key exposed during a recording or elsewhere.
After inspecting server errors and adjusting the response handling, the app generates posts from the blog. Eliason emphasizes that the working demo required several rounds of debugging.
Refinement and lessons
Add a prefilled post and learn from the process.
He adds a button that opens a prefilled post using a URL. It does not automatically publish; an API and additional controls would be needed for a different workflow.
His main advice is patience: start with a manageable scope, read errors, retry, and learn from recurring failures. A README or project rules can provide context when the task is more complex.
A novel and AI feedback
Eliason discusses fiction, editing and creative work.
Eliason describes his novel Husk, set in a fictional future where people live in a digital world and others maintain its infrastructure. The setting raises questions about identity and power.
For writing, he uses AI feedback on descriptions and dialogue, then reviews suggestions himself. He also reports that a whole-manuscript review helped him notice unresolved character threads.
His predictions about AI’s effects on creative jobs and productivity are personal forecasts, not measured outcomes. He expects people to keep making creative decisions while using new tools.
Más de este canal
46:40EN
17:50EN
15:03EN
33:09EN
13:05EN
1:06EN