DevDiscuss is a conversation podcast from DEV. Its subject is less any one programming language than the working life that grows up around code. Ben Halpern, a co-founder of Forem, hosts. In some episodes a Forem colleague joins him, either Abby Phoenix, the company's special projects manager, or Suzanne Aitchison, a senior software engineer there. Guests often come in pairs from different organizations. The questions are concrete. One episode asks how a conference talk proposal gets accepted, framed around Codeland, with two developer advocates, one of whom has served on a program committee. The advice is specific: answer what the call for proposals actually asks, make sure a talk billed as basic does not turn deeply technical, and do not count on popularity to carry a weak submission. Another episode looks at the everyday friction of working across departments. A GitHub software engineer and a TinySeed program director talk about remote communication channels that managers can mistake for lost productivity, and about how doing customer interviews can make someone a better engineer. Some conversations take a longer view. The SQL episode asks how many times an ordinary day touches Oracle, DB2 or SQL Server. It then follows Google's internal systems into Kubernetes, document stores and a database inspired by Spanner, and names two Google engineers, Jeff Dean among them, as people every engineer should know. Cybersecurity careers get a conversation with Alyssa Miller, a business information security officer at S&P Global Ratings and author of Cyber Defender's Career Guide. She talks about the noise around a supposed skills gap, and the episode argues that security people have to learn to speak to developers and users rather than blame them. The show also goes well beyond the job itself. In the episode on introducing kids to coding, leaders of two organizations that teach children describe putting logic ahead of syntax, starting from if-this-then-that reasoning everyone already understands. The heaviest material comes in an episode on how technology is used as a tool for abuse and coercive control. The conversation covers systems that were never designed to be nefarious but get used that way, and makes the case that information and dialogue, not fear-driven bans, keep children safer online. What a listener gets is less a tutorial than experienced people thinking out loud about problems developers actually run into. The closing credits invite listeners to start their own discussion on DEV with a post tagged 'discuss'. For a first listen, 'Getting Your Conference Talk Proposal Accepted' and 'Getting Along with Your Co-workers... All of Them' show the practical side most directly. The abuse episode shows how far the show's idea of a developer's concerns can stretch.