HackerTube

Lecture 1 - How to Start a Startup (Sam Altman, Dustin Moskovitz)

YC Root Access3 HN recommenders · recommended in 3 months, 2014–2024
YouTube
lecture · intro · evergreen · 2014–2024 on HN

The opening lecture of the How to Start a Startup course at Stanford, with Sam Altman covering ideas and products and Dustin Moskovitz discussing why to start a startup.

HN commenters recommend the series as timeless startup advice from strong speakers, and cite specific points from Altman and Moskovitz.

9 comments from Hacker News

@dgelks2023-01 · in “Ask HN: What's the best lecture series you've ever seen?”

▶ this video - How to Start a Startup 2014 by YC & Stanford Amazing set of speakers and pretty timeless advice for starting a startup

Strongly recommends View on HN
@karolsputo2021-04 · in “How People Get Rich Now”

Dustin Moskovitz presented that point in the invaluable How to start a startup series - ▶ this video A good resource when deciding on your future ambitions

Strongly recommends View on HN
@robertelder2016-08 · in “Ask HN: I am doing $2M annually as a solopreneur and need your help”

This lecture series specifically talks about the different problems faced at various stages of scaling, and it includes a lot of reputable people who have actually done it: link The YC series is of course good too: ▶ this video I'm not actually qualified to answer your question, but it sounds like you haven't discovered a bottleneck in your business yet, and until you do, you probably shouldn't hire any employees.

Recommends View on HN
@abetusk2024-07 · in “Ask HN: How to finish last 30% of a side project?”

The articles that are most relevant are probably ones from YC itself, along with ancillary material on startup woes, pitfalls, etc. Among the advice is how to validate ideas, is how to maintain momentum, knowing when to ship, when to wringing your hands and stop adding features, etc. Obviously geared towards startups and businesses but also applicable to projects. The pieces of advice that I try and follow (and often fail at following) are: * Commit to completing projects, not time. I'm bad at estimating time and putting time limits stresses me out. I prefer to work towards a goal rather than a time limit. * Be vicious about removing features that are superfluous to the main project in order for it to ship. "Nice to have" features can be added later. A mediocre project that ships and can be improved later is better than a perfect project that never ships. * Get some space. Getting a little burnt out is easy to do and almost inevitable. Even taking a day or week away sometimes recharges my batteries. The hopelessness I feel about the amount of effort required to complete seems less daunting once I've recharged. This is even better if it ships because the daunting extra "nice to have" features, refactoring or complete architecture overhaul seem less daunting when I'm rested and recharged. * Don't get into "all or nothing" elements. Break up large projects into smaller manageable pieces as much as possible. Insofar as is possible, have smaller "shippable" elements that contribut

@headcanon2020-11 · in “The Truth About Starting a Startup”

Thats a really cynical interpretation of YC - There's a ton of risk with starting any business, tech especially. You could say the same about any angel or early stage investor or accelerator program. PG and Sam Altman have always been upfront about the risk and expected returns from one of these - in the Startup Class, Altman even says that if your goal is highest expected returns you should go work at a FAANG [1] [1] ▶ this video