Going solo should be the rule, not the exception
The article argues that going solo—whether for travel, dining, or other activities—should be normalized and considered the standard rather than the exception, challenging societal stigmas around doing things alone.
Background
- This video argues that working or pursuing projects alone (solo) should be the default approach, rather than constantly seeking collaborators or teaming up. It pushes back against the common tech/startup culture assumption that "you need a co-founder" or that good work requires a team.
- The speaker is likely drawing on the "solo founder" philosophy popularized by figures like Peter Thiel (who said "solo founders are underrated") and more recently by the indie hacker / solopreneur movement on platforms like Twitter and YouTube. This community values independence, full ownership, and rapid personal iteration over the overhead of managing people.
- Key prior context: In startup investing, VCs traditionally prefer teams (to distribute risk and ensure resilience). A solo founder is often seen as a red flag. This video challenges that norm, aligning with a newer wave of builders who bootstrap alone and avoid VC funding entirely.
- Why it matters: The trade-off is speed/control vs. support/burnout. Understanding this debate helps make sense of the broader "build in public" and "indie hacker" subculture that has grown around tools like Gumroad, ConvertKit, and AI coding assistants.