Talking Code

Jeff Patton, author of User Story Mapping, teaches us how to map user stories by focusing on the user's journey to an outcome. He shares his opinion on the notorious "MVP" and how he helped Gary Levitt build his MVP with Mad Mimi.

Michael Bernstein of Code Climate explains how to monitor your code's quality with static analysis. He tells us how you can maintain or improve quality over time, and what you can do to fix poor code.

Anthony Thomas tells us how he made the leap from manufacturing to starting a tech team at Sticker Mule. He explains why your first developer is so critical to your founding team.

Tom Dale tells us about building modern web applications that are becoming increasingly like native apps. We discuss JavaScript frameworks like Ember and the future of the web.

David Cramer tells us how to catch and fix critical errors that can affect your bottom line. We also discuss the key differences between exceptions and bugs, and how to handle errors gracefully.

Randy Rayess tells us when and how you should outsource development of your software, how to reduce your risk, and the way your team should think about feature prioritization.

Brad Van Vugt and Matt Harris talk about transactional emails – how to send your users emails they'll act on at critical moments in your application's lifecycle.

Justine Jordan explains how your company should treat email, the difference between designing for email and the web, and what you can do to up your open rates.

Fred Stevens-Smith of Rainforest explains the need for quality assurance testing and how to actually do it in the resource constrained environment of a startup.

Jordan Gal of CartHook talks about how he found his technical co-founder, how he de-risked his app before building it, and the tension between business and technology requirements.