How Not to Break a Simple Idea
summary
Roadmap-first claim: get to a Minimum Viable Product quickly, keep it lean, refactor later. Practical tool choices: Laravel/Lumen, Nova for admin, pick packages carefully and use Forge and GitHub to deploy instead of DIY servers. Real builds include a timesheet system with a contentious query but shipping success; expect lots of failure and iteration. Personal workflow tip: a five-day phone experiment (no screens after 7:30) to improve focus and output.
AI-written summary · about
chapters (30)
- 0:00Intro
- 2:36Problems
- 6:10Planning
- 9:32Roadmap
- 12:52Lean
- 14:09Stick to plan
- 14:32Visualize your journey
- 15:15My Note
- 17:58MVP
- 18:34KISS
- 19:59Resources
- 21:48Its not about coding fast
- 24:00Burnout
- 25:23Toilet time
- 25:49Sleep
- 26:46Work Week
- 28:21Go to Bed Sober
- 29:51Turn Off Your Phone
- 31:46Earthing
- 36:03Content
- 38:19The choice
- 40:12CSS
- 41:28Learning new things
- 42:20Learning resources
- 43:27Not all opinions are right
- 44:00A bit of code
- 45:26Youre not alone
- 46:14Youre going to fail
- 46:51Thomas Edison
- 47:16On the internet
related talks
26mHacks to Work More Efficiently- Rain Leander
27mStop overthinking and go create things
29mNo more tears from project nightmares
25mBuild Failed Startups—Not Side Projects
26mConcept to Execution Delivering a Product
09mLeading a team through 0-1 product development
21mNeed for speed - Moving fast as a software engineer
35mYou're not Jesse James