Ernesto and I talk about how he learned software development, but also some business and management in his competitive public university in Argentina. We talk group projects, learning well and trying things that failed.

I met John Pavan early in his career, after he'd just made the transition from nuclear physics to full-time computer programming. We caught up on how C++ is doing and how he's doing in it. We also talked about what he looks for in a software hire, and handling legacy code.

Chris Seaton, founder of TruffleRuby, talks with me about getting a computer science Ph.D, how learning compilers is necessarily like an old-style apprenticeship, and a near-the-metal view of complex algorithms for computation.

Michael Dominick, of the Mike Dominick Show, talks to me about patterns in software, the Pokemon API, what he looks for when hiring developers and how he's pretty sure the universe is POSIX compliant.

George and I talk about how he learned to do what we do. He loved his classes on security, and I'm envious. He doesn't remember his classes on mathematics — I might envy that, too. We talk about how hard making good games is, a little. And we talk about how you need to think of each job as a stepping stone to the right next thing.

Jared and I talk about his journey through all sorts of programming platforms, from the Commodore 128, through PHP to Ruby and onward. He talks about Object Oriented programming, Rails service objects and why he doesn't like classes that are just functions. He talks about how GitHub brings a little of the benefits of pair programming to the single-programmer experience. We even talk a little language performance, and how machine learning code looks weirdly like graphics and GPGPU.

In this episode, Chris and I talk about the black magic of video game timing, why you should build your own package manager, why you should write what you love, why Chrome using All The Memory is a good thing and what you can learn from Porsche redesigning their whole car every four years.

In this episode, Drew and I talk about job interviews, static and dynamic languages and a little of everything career-related.

Most developers don't write, and most don't need much theory. Universities don't want to teach you to shovel. The very best heads-down developer in the world is still one you've never heard of. Having a balance of seniority on a team makes a better team. Writing is important: a good StackOverflow answer can save a lot of minutes.

Swizec and I talk about his theory-heavy education in Slovenia and how extremely useful it's been to him. We also talk about educational overengineering, automata theory, why NoSQL is usually a mistake and whether online education has jumped the shark.