Andrew Ng

Sources#

• Thread by @AndrewYNg

Summary#

One of the most widely-read educators and practitioners in machine learning: founding lead of Google Brain, co-founder of Coursera, former Chief Scientist at Baidu, founder of DeepLearning.AI and Landing AI, managing general partner of AI Fund, and adjunct professor at Stanford. He writes The Batch, a weekly letter that is one of the field's highest-circulation practitioner venues. On X as @AndrewYNg.

The wiki knows him through a single June 2026 letter, cross-posted to X, on how he builds 0-to-1 products with coding agents.

The June 2026 letter#

Written as a response to "loop engineering" becoming a buzzphrase after Boris Cherny and Peter Steinberger went viral — the same two quotes Loop Engineering is built on. Ng's move is to point out that everyone is optimizing one loop while a product runs on three.

• The Three Loops of AI-Native Building — the agentic coding loop (agent-closed, minutes), the developer feedback loop (human-closed, tens of minutes to hours), the external feedback loop (market-closed, hours to weeks). Each outer loop is one to two orders of magnitude slower than the one it contains. "These loops guide not just how I build software, but also how I decide what software to build."
• Context Advantage, Not Taste — the letter's sharpest line, and a direct reframing of the wiki's central open question. "Many people describe this human contribution as 'taste,' but I prefer to think of it as humans having a context advantage, since that gives us a clearer path to helping AI systems get better… So long as the human knows something the AI does not, human-in-the-loop is needed."
• QA was the job that went away. "Last year, a lot of developers (including me) were acting as the QA function for our coding agents… with coding agents much more able to test their own code, the amount of time we need to spend on this function has decreased significantly." The human was promoted out of QA, not removed from the loop. This runs against Verification as the New Bottleneck and against Faros's telemetry; the scope difference (personal 0-to-1 builds vs production orgs) is the likely reconciler.
• Evals as a reaction, not a prophylactic. "If you find that the system repeatedly runs into certain problems, building a set of evals for the agent becomes useful." Cheaper and lazier than Cat Wu's "ten great evals" as the spec.
• Engineers into product. "More engineers are starting to play a partial product management role… the hardest part is shaping the product vision and striking a balance between building and getting user feedback." A third independent report of Engineer PM Convergence, with a named failure mode: engineers over-run the loop they enjoy.

His running example is a typing-practice app he built for his daughter over a weekend, in which the coding agent worked unattended "for around an hour, using a web browser to check what it had built multiple times before getting back to me." An anecdote, not a measurement — everything in the letter is practitioner-opinion.

Connections#

• The Three Loops of AI-Native Building — his taxonomy; the wiki's map of what loop engineering leaves untouched
• Context Advantage, Not Taste — his reframing of the residual human role as an information asymmetry rather than a faculty
• Loop Engineering — the discipline he is placing and bounding; he credits Boris Cherny and Peter Steinberger with naming it
• Engineer PM Convergence — third independent vantage on the same role merge, after Cat Wu and Boris Cherny
• Research Taste as the Human Bottleneck — the page his "context advantage" aside argues is asking the wrong question
• Andrew Ambrosino — published "loops are so last week" the same week Ng published a loop taxonomy; the two disagree only if you conflate harness-loops with product-loops

Sources#

• Thread by @AndrewYNg — Andrew Ng, The Batch (2026-06-30), clipped from X (practitioner-opinion)