TSMC Founder Morris Chang
We flew to Taiwan to interview TSMC Founder Morris Chang in a rare English interview. In fact, the last long-form video interview we could find was 17 years ago at the Computer History Museum… conducted by the one-and-only Jensen Huang! This episode came about after asking ourselves a version of the Jeff Bezos “regret minimization” question: what conversations would we most regret not having if the chance passed Acquired by? Dr. Chang was number one on our list, and thanks to a little help from Jensen himself, we’re so happy to make it happen. Dr. Chang shares the stories of a few crucial moments from TSMC’s history which have only been written about in his (currently Chinese-only) memoirs, including how TSMC won Apple’s iPhone and Mac chip business and a 2009 discrepancy with NVIDIA that
Could not retrieve the full article text.
Read on Acquired Podcast →Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Releases
How 2 downed jets show a critical vulnerability for the US as Iran war rages on
One crew member from a US fighter jet shot down over Iran has been rescued by US forces, multiple news outlets reported on Friday, citing two US officials, while a second crew member remains missing. A separate US aircraft was also hit near the Strait of Hormuz, though its pilot was rescued safely, according to the reports. Iran on Friday claimed to have shot down an American fighter jet, releasing photos of apparent wreckage of an F-15E, while the United States reportedly launched a...
Stop Writing Rules for AI Agents
Stop Writing Rules for AI Agents Every developer building AI agents makes the same mistake: they write rules. "Don't do X." "Always do Y." Rules feel like control. But they are an illusion. Why Rules Fail Rules are static. Agents operate in dynamic environments. The moment reality diverges from your rule set it breaks. Behavior Over Rules Instead of telling your agent what NOT to do, design what it IS: The system prompt (identity, not restrictions) The tools available (capability shapes behavior) The feedback loops (what gets rewarded) The memory architecture A Real Example I built FORGE, an autonomous AI agent running 24/7. Early versions had dozens of rules. Every rule created a new edge case. The fix: stop writing rules, start designing behavior. FORGE's identity: orchestrator, not exec
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!