field not statedblog
Kevin Yang
What they did
Yang used Claude Code for several weeks to perform the data analysis for a paper he was working on and estimates it generated over 98 percent of the code. His setup pairs Claude Code in a terminal with Cursor for reviewing generated code, Jupyter for notebooks and lazygit for version control; he compared Codex CLI, Gemini CLI and Cursor agent and found Claude Code best at that time. He organises each project as plan files for data cleaning, per-question analysis and output generation.
In their words
"Ultimately, I believe it generated over 98% of the code."
"Although CC is magical, it won’t always produce the output that you want, and it makes mistakes all the time."
"A more effective approach for me is to make a plan for your project first, then focus on smaller tasks one at a time."
Lessons they draw
- Use git to see what the agent changed and to roll back (Yang).
- Plan first, put the plan in a markdown file you can edit, and work in small tasks; the file also serves as persistent context and documentation (Yang).
- Review generated code in an editor and correct errors; effective use is about aligning the agent with your expectations (Yang).
Limits of this account
An early (July 2025) account whose model comparisons are dated; no description of verification of results, and his field is not stated.