
Sign up to save your podcasts
Or


Martin Klose talks with Eberhard Wolff about Coderetreats - events where developers practice development techniques to become better programmers. He explains how to join such events and what it takes to do your own Coderetreat.
Alex Budzier of the Oxford Saïd Business School and Jürgen Laartz of McKinsey Berlin join Robert Blumen to talk about the their research on large IT project failures. Why do large projects fail and to what extent are these failures avoidable?
SE Radio Host Stefan Tilkov talks to Vaughn Vernon about the topic of his most recent book, Reactive Messaging Patterns with the Actor Model. Vaughn explains the concepts and history of reactive programming, the actor model and its consequences, actors and their relation to object orientation, a typical approach for designing a system made of actors, Scala/Akka and Erlang, and the role of enterprise integration patterns.
Johannes Thönes talks to Axel Rauschmayer about JavaScript and ECMAScript 6. They talk about the origin and version history. Then they dive into key JavaScript concepts and explain the features coming into the language with ECMAScript 6.
Sven Johann talks with Andrew Phillips about DevOps. First, they try to define it. Then, they discuss its roots in agile operations, its relationship to lean development and continuous delivery, its goals, and how to get started. They proceed to system thinking and what "You build it, you run it" means for a system when developers have pager duty.
They continue with the diversity of DevOps requirements among companies and industries; copying ideas versus finding your own way; culture, mindset, and recommended practices; and the mandatory tool chain. They wrap up by discussing architectural styles that support DevOps and DevOps costs versus benefits.
John Wilkes from Google talks with Charles Anderson about managing large clusters of machines. The discussion starts with Borg, Google's internal cluster management program. John discusses what Borg does and what it provides to programmers and system administrators. He also describes Kubernetes, an open-source cluster management system recently developed by Google using lessons learned from Borg, Mesos, and Omega
Charles Anderson talks to John Sonmez, the author of Soft Skills—"the software developer's life manual." They start out discussing the book and what it covers, which is pretty much everything in a developer's life outside of code. The book contains seven sections; they discuss two of them: "Career" and "Marketing Yourself."
John discusses the value of specializing in your career without being overspecialized. He describes how to "hack the interview process" to either reduce the need for an interview or build a strong relationship before the interview.
He then discusses how software developers can market themselves to achieve career goals. His recommendations include blogging, attending user groups, and presenting at conferences. Although most of his recommendations are intended for long-term results, he also discusses what to do in the short term for someone who needs to find a job quickly.
Gernot Starke talks about arc42: an open-source set of templates he developed to document software architecture based on his practical experience with real projects. Also Gernot and host Eberhard then discuss how documenting architecture fits into agile processes and how to find the right amount of documentation for a system. They walk through the different parts of the arc42 templates covering requirements and the context of the system and the solution structure, including building blocks, runtime, and deployment. They discuss tooling, versioning, testing documentation, and how to keep documentation up to date.
Slava Akhmechet and Jeff Meyerson discuss RethinkDB, an open source database for the real-time Web. RethinkDB pushes data to the application rather than requiring the application to poll the database for updates. The discussion begins with the question of why databases need to be rethought–why is it better to build JSON-pushing into the database layer rather than the application layer? Slava explains how RethinkDB changes a full-stack architecture and discusses how Meteor's JavaScript framework is a good model for how to think about applications which use push. The discussion continues with an exploration of RethinkDB's transaction model, its data model, and its guarantees. The conversation concludes with an exploration of tradeoffs between different programming languages. Slava explains why RethinkDB was written in C++ rather than Go, or another language.
Sven Johann talks with Dave Thomas about innovating legacy systems. Dave clarifies first why legacy systems are both valuable and problematic. Next, they discuss bad systemic and good incremental approaches for innovation of legacy systems; why you shouldn't rewrite an old system but rather focus on tactical changes to reduce cost or increase productivity within one quarter; examples of how to measure success of the innovation; how to get full support from management to use any technology you want; when cleaning up the codebase makes sense and when not; good ideas to innovate the codebase; approaches to introduce tests; and how to deal with data