The Talking Code podcast contains short expert interviews that help you decode what developers are saying. We help non-technical founders, designers, project managers, or anyone who needs a 30,000 foot view of how to run a successful software company.
How to Become an Effective Junior Developer
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.
Making the Most of Your Analytics
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.
How to Deliver a Successful User Experience
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.
Going from Junior to Senior Developer
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.
Using Data to Make Informed Product Decisions
Lincoln Ritter, director of engineering at Animoto, shares how they use data to make more informed product decisions.
How to Do Information Architecture
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.
Well-Rounded and Informative
There is a lot surrounding the world of software development and these two are on a mission to cover it all. Business, hiring, code quality… the list goes on. Great stuff.
Poor audio quality
The poor audio quality of the lost recent talk about junior developers is really annoying... it made the episode unlistenable.
Clear delivery of concepts
Everything in computing can be talked about in layers of abstraction. The problem is knowing what layer of detail to jump into when talking about a subject. Diving too far into the technical detail can create blinders for developers that are new to a concept.
Josh and Venkat seem to really understand that and do a wonderful job of structuring the interview to exposing you to an idea/concept/method/tech in a clear way by asking the right questions (see:“clarifying questions”). You can later figure out how to incorporate things into your unique projects.
This interview style empowers you without overwhelming you and that, at least for me, is the reason I enjoy Talking Code.
Bravo guys, keep up the good work!