Code is not important... or is it?
summary
Builds an "organization map" product iterating from PDF to spreadsheet to Airtable then a custom backend, proving experiments by using Google Sheets, Airtable, Sequel and Sinatra before migrating to ES6 React and Redux on Rails. Claims experiments accrue $50,000 of tech debt representing ~12% of the codebase but justify it as learned product knowledge. Shows a running Mailtrap case where attachments consume 85–90% of DB storage, so files move to S3 and APIs change. Emphasizes just-in-time refactoring, ticketing tech debt, and measuring trends with Code Climate.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:33Code beyond problem solving
- 7:10Product story and experiments
- 11:25Building product vision
- 17:28Growing supporting structure
- 23:49Maintaining code quality
- 30:14Managing tech debt
- 39:50Wrap-up and key takeaways
- 44:51Q&A on organization
related talks
28mBreaking Rules to Ship Products: A Beginner's Rails Journey
30mMaintaining Sanity and Code
27mStop overthinking and go create things
37mStaying passionate about your craft
44mIts all About the Journey
42mThe Monster Coming Over The Hill
48mMind of a Hacker
48mThe Effective Software Architect - Work Smarter, not Harder