Talking Code

Louisa Barrett of Haught Codeworks tells us about how to become an effective junior developer. We also speak in depth about how to become a better teacher.

Diana Smith of Segment tells us how to get the most out of our analytics tools. In the pursuit of trying to be data-driven, we have been conditioned to track everything. Diana tells us why this can be dangerous if we want to draw useful insights from our data.

Sarah Doody, a UX designer, consultant, and writer, tells us how to build products with great user experiences. We will hear why user experience is far more important than design.

Mubashar Iqbal, the #1 product maker on ProductHunt, tells us about how he launches products that people use in weeks, not months.

Ben Orenstein of Upcase tells us how to go from a junior to a senior developer. He reveals a number of things senior developers do that junior developers don't.

Lincoln Ritter, director of engineering at Animoto, shares how they use data to make more informed product decisions.

Abby Covert, author of How to Make Sense of Any Mess, teaches us about information architecture, a subject she strongly feels is a core life skill. She's seen people get fired over language and informs us that – quite obviously in hindsight – architecture is less expensive than design.

Sven Lenaerts joins us to share his expertise on product design and user experience. This conversation includes some thoughts on MVPs, when to hire a designer, and what a product person really does.

James Ward shares how the hosting landscape has changed for web applications over the years and how you can avoid some of his middle-of-the-night pager nightmares.

Jonathan Cornelissen tells us about DataCamp, the need for data scientists, and how to become one yourself. We also learn about some popular languages and libraries for analyzing data.

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.

Dave Hoover on coding bootcamps and how immersive learning environments are helping to fix the developer talent shortage. Plus: should you learn to code?

Basecamp's Ryan Singer on the difference between UI and UX, how to build meaningful solutions for problems and people, and what it means to "scratch the itch."

Sandi Metz on how OOD (objected-oriented design) and agile development simplify design requirements, promote communication and lead to better, faster, more cost-effective software.

Florian Motlik on how testing and validation using the continuous integration and deployment model results in manageable, quality software.