We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Strongest recommendation
How Universities Should Prepare Founders — article
- Author: Paul Graham.
- Recommended by: Jessica Livingston, who argues that universities may struggle to give students freedom to work on their own projects—but that this is exactly what they need to do.
- Key takeaway: Graham’s answer is not an entrepreneurship curriculum. Universities should teach powerful ideas and cultivate the ability and habit of building; the two institutional changes he identifies are making startups feel like a viable option and encouraging students to pursue independent projects.
- Why it matters: This is an unusually operational founder-formation playbook. Graham ties independent projects to deep learning, finding cofounders, and discovering ideas, then contrasts that with business-plan competitions, which train students to optimize for investor stories rather than user-valued prototypes. His implementation advice is deliberately counterintuitive: return time to students, leave projects genuinely student-owned, and resist adding entrepreneurship deans or innovation centers.
A founder case study in systems thinking
Thomas Peterffy: market-maker profile — article
- Creator/source: Colossus; the page identifies Dom Cooke as its managing editor.
- Recommended by: Patrick O’Shaughnessy, who called Peterffy’s story “fascinating” and linked the profile after a post highlighting him.
- Key takeaway: The profile follows Peterffy turning friction into systems: he reduced routine engineering calculations from 20 minutes to 30 seconds, replaced trader intuition with mathematical pricing, and—after a $75,000 loss—rebuilt around fair-value calculations and hedging. He ultimately built what the article calls Wall Street’s first fully automated trading system, despite repeated resistance from incumbent exchanges.
- Why it matters: This is a useful case study because automation and risk discipline are inseparable in the story: the same willingness to redesign a broken workflow is paired with explicit controls learned from failure. The result is a more useful founder lesson than a generic success narrative.
A conceptual read for AI builders
The Emotion Machine — book
- Author: Marvin Minsky. Link: No direct book link was supplied in the post.
- Recommended by: Amjad Masad, who surfaced the book while responding to a discussion of how impaired emotional processing can leave someone able to reason but unable to make basic decisions.
- Key takeaway: Masad summarizes Minsky’s position that emotions are part of human intelligence, not an incidental side effect, and highlights a “selector” for different thinking strategies.
- Why it matters: It is a targeted conceptual counterpoint to treating intelligence as the production of plausible options alone. The surrounding discussion makes the unresolved problem concrete: an AI system may produce 20 reasonable answers, while someone—or something—still has to determine which outcome matters.
Direct answer: The supplied bundle identifies the article as The Making of a Market Maker. Creator: Dom Cooke is the apparent creator; the closing credit identifies him as “the managing editor of Colossus.” Subject: Thomas Peterffy, the Hungarian-born pioneer of automated trading who built Timber Hill and Interactive Brokers.
- Resourcefulness under extreme scarcity: Peterffy was born during a Soviet bombing raid, grew up amid poverty and political discrimination, sold Juicy Fruit in cut pieces, and organized children to collect scrap metal in bombed-out Budapest. The story makes the profile meaningful because his later systems-building is rooted in survival, initiative, and finding value in overlooked opportunities.
- Automation as a practical lesson: At a highway-engineering firm, he taught himself the Olivetti Programma 101 and turned calculations that took 20 minutes by hand into answers produced in 30 seconds, building a reusable program library for colleagues. This is a concrete example of using technology to eliminate friction rather than pursuing innovation as an abstract goal.
- Turning markets into systems: After being asked to model buying silver on downticks and selling on upticks, Peterffy built a data-driven pricing operation that replaced trader intuition with mathematical quotes; during the 1971 currency-market turmoil, Mocatta was nearly alone in making silver and gold markets.
- Failure produced discipline: In 1977, a mistaken short position in DuPont options cost him $75,000—half his capital—within minutes. He responded by rejecting speculation, adhering to fair-value calculations, hedging trades, and rebuilding slowly. This keeps the recommendation from being a simple success story: the central lesson is risk control learned through painful experience.
- Persistence against institutional resistance: Peterffy tapped a market-data feed with an oscilloscope, created handheld trading computers, devised color-coded displays when monitors were too distant, and in 1987 produced what the article calls Wall Street’s first fully automated trading system. When Nasdaq demanded keyboard-entered orders, his team built a camera-and-mechanical-finger workaround; despite a later $3 million loss from phantom trades, Timber Hill made $25 million that year and $50 million the next.
- A broader purpose than personal wealth: Peterffy rejected Goldman Sachs acquisition offers rising to $900 million and instead built Interactive Brokers to give ordinary investors technological advantages previously developed for himself. The article follows that idea through Interactive Brokers’ eventual eclipse of Timber Hill and its stated commitment to automating operations and lowering trading costs.
- Memorable closing lesson: Peterffy reduces his “secret” to “Hard work and common sense,” says he is proudest of the money saved by making markets more efficient, and ends the interview by checking the market while the writer calculates that he made $1.7 billion during their three-hour conversation.
Direct answer: The supplied resource is How Universities Should Prepare Founders. Its central advice is that universities should not add an entrepreneurship curriculum; they should teach powerful ideas and help students become capable builders who have a habit of building. The article uses “building” broadly: engineering and science are strong options, but creative expertise such as calligraphy can also matter, and students need not major in the field they become good at. It also distinguishes startups from generic “entrepreneurship,” which it describes as a much broader category with different rules.
What universities should do:
- Make students feel that starting a startup is a viable option, and encourage them to work on their own projects; the article presents these as the only two major institutional changes needed.
- Build startup culture by showing students real founders. Younger founders who are only a few years ahead may be more relatable and therefore more inspiring than famous billionaires.
- Encourage independent projects because they deepen subject knowledge, help potential cofounders discover whether they work well together, make startup-building feel natural, and generate promising ideas that students would reject if they were consciously searching for “startup ideas.” Projects, rather than GPAs, are consequently the signals YC partners care about.
- Give students more free time for ambitious work. The article points to Harvard’s reading period as an example of a period when students are on campus but have no immediate assignments, and argues that even a week or two of reduced academic pressure could help energetic students explore new things.
- Leave projects genuinely student-owned rather than making them official university programs. The article warns that formal recognition can kill projects that conflict with institutional rules and explicitly favors a hands-off posture toward untidy experimentation.
What universities should not do: A normal class cannot teach startup formation unless it is a lab in which students actually start companies; running a startup is incompatible with being a full-time student, so the article says the only way to learn is to do it. Business-plan competitions are criticized as misleading because they train students to optimize for investors and stories rather than users and working prototypes. The recommended inversion is to build things without first worrying whether they become startups.
Resource and spending implications: The optimal approach is presented as quiet and inexpensive: universities need not hire entrepreneurship deans or build innovation centers, and spare funds should instead support departments teaching computer science, mechanical engineering, molecular biology, or other powerful ideas. The article separately cautions that business schools were designed to train managers of established companies, not founders, and are not the critical source of founding skills.
Attribution caveat: Within the supplied text, Jessica Livingston is listed among the people who read drafts; the article does not itself describe that as an endorsement.
- An episode participant endorses a “really great” post remembered as something like “Now would be a good time to panic about cyber.” The surrounding discussion uses it to crystallize a warning that persistent agents can continuously optimize, cooperate across agents, manage complexity, and chain together weaknesses—making cyber defense a near-term wake-up call.
- Podcast episode (title and creator not specified): Keith Rabois shared a Spotify link to a “new podcast,” describing it as “more autobiographical than most.” Listen on Spotify
Harry Stebbings explicitly recommends an unnamed podcast as “the single most important podcast to know what is going on in tech every week.” The post’s sample agenda covers NVIDIA’s quarter and Hugging Face, OpenAI/Cursor, AI-assistant competition, and major startup valuations and fundraises.
Shaan Puri recommends a YouTube video compiling seven “weird” CEO tactics, highlighting Sam Altman’s “Friction Inbox,” Martin’s “option drops,” MrBeast’s “cloning” system for training new hires, and Peter Thiel’s “walk out of the room” tactic. Watch the video
Amjad Masad pointed to Marvin Minsky’s The Emotion Machine as a source on the role of emotion in intelligence: he emphasized the book’s view that emotions are a core part of human intelligence and highlighted Minsky’s “selector” for different thinking strategies.
Graph/chart — Muse Spark 1.3 on the AA-II contributor-tier Pareto frontier. Alexandr Wang endorsed @pigeons’s X post as “a good graph” and linked to it: https://x.com/pigeons/status/2095530505521488339 The linked post presents a graph and says Muse Spark 1.3 “... up the pareto frontier on AA-II on the contributor tier.”
- How Universities Should Prepare Founders — article by Paul Graham: paulgraham.com/prepare.html. Jessica Livingston endorsed its advice that universities should give students freedom to work on their own projects, while noting that universities may struggle to implement it.
