Translation and notes
A readable adaptation of the article's core ideas, with the original source clearly credited.
This essay is useful because it looks at the period before a company exists, when someone is beginning to imagine becoming a founder. The practical warning is that startup work behaves differently from many familiar systems. Habits that help in school or larger organizations can mislead an early founder, especially the habit of trying to look successful before anything real is working.
The first discipline is judgment about people. Before choosing a cofounder, employee, investor, or partner, do not let impressive credentials override real reservations. A small company amplifies trust problems. A relationship that feels slightly wrong in a calm moment can become a serious operating risk when pressure rises.
The second discipline is to become expert in the user and the problem, not merely fluent in startup language. Fundraising mechanics, legal structures, and pitch craft can be learned when needed. They are dangerous when they become substitutes for the core work: learning what users struggle with and building something they pull toward.
The third discipline is timing. A startup is not a polished side activity; if it works, it can absorb years of attention. Preparation can therefore mean doing hard real projects, learning powerful domains, and working with people you respect before committing to a company. Better ideas and better cofounder relationships often emerge from that kind of work.
Selected advice from the article
- Write down the user problem and the behavior that proves it is real.
- Test cofounder trust through real work before formal commitment.
- Learn startup mechanics when they become necessary, but do not let them replace user understanding.
- Separate activities that only look like a startup from activities that create learning, product pull, or trust.
Operating takeaways
- Founder preparation starts with real exposure to users and problems.
- Trust in key people is an operating requirement.
- Startup theater can hide the absence of product pull.
- Hard side projects and deep learning can be better preparation than premature incorporation.
Quick feedback
What did this article make clearer for you?
Choose a reaction or share a question or experience. Useful responses can shape future notes.
This is a free adaptation, not a word-for-word republication of the original article.