# Paul Goldsmith-Pinkham

- Researcher: Paul Goldsmith-Pinkham
- Role: Associate Professor of Finance, Yale School of Management; Faculty Research Fellow, NBER (as stated by Markus' Academy)
- Field: economics
- Tools: Claude Code; Cowork; GitHub; Overleaf
- Published: 2026-03-29
- Source: https://markusacademy.substack.com/p/claude-code-for-applied-economists
- Latest flagship models when written: Claude Opus 4.6 and GPT-5.4. Latest now: Claude Opus 5.5 and GPT-6.1 Sol.

## What they did

This is a newsletter summary of an eight-episode Markus' Academy mini-series in which Goldsmith-Pinkham teaches Claude Code to applied economists, covering getting started, data analysis, planning, sub-agents, large datasets and verification. In an example, he used Claude Code to obtain and plot data on US home ownership, shrinking the gap between a vague idea and first results. In a replication of Jay Ritter's results on post-IPO stock performance he showed verification practice: integrate with GitHub so the project is a chain of committed steps reviewed one change at a time, and connect the repository to Overleaf so Claude updates figures and tables.

## In their words

> "The core principle: every number in a draft should come from the code, not from an AI’s memory."

> "Paul showed how Claude Code dramatically shrinks the gap between a vague research idea and initial results."

## Lessons they draw

- Every number in a draft should come from the code, not from the AI's memory (as summarised by Markus' Academy).
- Review the agent's work as a chain of committed steps, one change at a time (as summarised by Markus' Academy).
- Context window and compaction matter for how the tool is used (as summarised by Markus' Academy).

## Limits of this account

Secondary report: the quotes are the newsletter's sentences summarising Goldsmith-Pinkham, not his own words; his own notes and videos were not read.
