Article·7 min read

Andrej Karpathy: Software Is Changing Again. What Should Engineers Learn?

A practical reading of Karpathy’s AI Startup School keynote: what changes when models can write code, and why taste, context, and verification still matter.

By Chakri AI Research

Andrej Karpathy: Software Is Changing Again. What Should Engineers Learn?

In his June 2025 AI Startup School keynote, Andrej Karpathy describes a change in the software-building interface: developers can increasingly express intent in natural language and ask models to produce working code. The useful takeaway is not “programming is over.” It is that more of the work moves into specifying the goal, steering the system, and deciding whether its output is good enough.

The work shifts up and down the stack

When code generation becomes easier, the bottleneck often moves to understanding the problem, giving the model the right context, recognizing a weak design, and checking whether the result behaves correctly. A model can produce a plausible implementation quickly; it cannot make the product trade-offs meaningful without someone who understands the user and the system.

A useful way to adapt your engineering practice
Still mattersWhat changes with AI assistance
Fundamentals: data structures, APIs, security, testingYou may ask a model to draft routine implementation faster
Understanding users and requirementsYou can explore more prototypes before committing
Code review and debugging judgmentYou review a larger volume of generated changes
Clear communication and collaborationMore work starts from written goals and constraints

The career signal: show the full loop

For an early-career engineer, a strong portfolio project should show more than a prompt and a screenshot. Explain the problem, show the code or demo, describe how AI helped, list the tests you ran, and point out a limitation you found. This gives a reviewer evidence of both technical ability and judgment.

The keynote is one experienced researcher’s view of a fast-changing craft, not a forecast that every coding task—or every engineering role—will disappear. Treat it as a prompt to update your workflow: use AI where it helps, keep learning fundamentals, and make your verification visible.

Sources and further reading

Specifications and prices can change. Check the linked pages before making a purchasing or deployment decision.