The O'Reilly Media Podcast spreads the knowledge of innovators. At O’Reilly, a big part of our business is paying attention to what’s new and interesting in the world of technology. The O'Reilly Media Podcast features interviews with the people working on the forefront of technology.

O'Reilly Media Podcast

Podcast

Architecture

O'Reilly's Mac Slocum talks with Neal Ford, a software architect and meme wrangler at ThoughtWorks, about software architecture, its relationship with DevOps, and the growing influence of microservices.

How The DevOps Revolution Informs Software Architecture

O'Reilly's Ben Lorica chats with Poppy Crum, neuroscientist and researcher at Dolby Labs, about AI and virtual reality systems, and about building a team of researchers from diverse disciplines.

Understanding Neural Function and Virtual Reality

Laura Klein and Kate Rutter chat about what is wrong with personas and how we can make some important tweaks in order make them more useful for design and communication.

This podcast is a cross-post from the User’s Know podcast (http://www.usersknow.com/podcast), and is republished here with permission. The podcast also is available on iTunes (https://itunes.apple.com/us/podcast/what-is-wrong-ux-users-know/id980133198).

Tweaking Personas: Mastering the Hunt for the Ideal User

O'Reilly's Rachel Roumeliotis chats with Joost Visser, head of research at Software Improvement Group (SIG), about how a focus on quality helps to achieve the fastest possible schedules and lowest possible cost of development and maintenance.

Better Code is Cheaper

O'Reilly's Mary Treseler chats with designer Gretchen Anderson about using design as a force to improve our lives and about approaching design as an inclusive discipline.

Design for the Greater Good

Rachel Roumeliotis talks to Intel's Chuck Freedman and Iman Saleh about the data analytics applications of the Trusted Analytics Platform (TAP).

The advantages of open source in analytics

Deployment frequency, development lead time, MTTR, MTBF, code coverage, cycle time -- these metrics, like all metrics, can be absolutely key or utterly meaningless. Don't just ask which metrics to use. Ask how to use these metrics to deliver better software, faster.

CodeTalk Ep. 5: DevOps Metrics That Actually Mean Something (Anders Wallgren, CTO of Electric Cloud)

In this episode of the O’Reilly Podcast, I sat down with Hugh McKee, solutions architect at Lightbend. McKee and I discussed why the actor model is an ideal choice for building today’s distributed architecture, how actor-based systems manage requests to perform tasks, the kinds of enterprises already having success with actors, and best practices for getting started with asynchronous systems.

Understanding Reactive Architecture Through the Actor Model

In this episode of the O’Reilly podcast, Jon Bruner sat down with Rahul Kamdar, director of product management and strategy at TIBCO Software. They discussed the shift from the centralized enterprise service bus (ESB) to a distributed data architecture based on microservices, APIs, and cloud-native applications.

From Enterprise Service Bus to Microservices

This week's podcast features Simon Brown well known for his work training software architects. Topics include the differences between a tech lead and an architect, how much documentation is enough and what that looks like in a continuous delivery environment.

What you'll learn on this podcast:
•	As an industry we seem to have lost our knowledge of how to do architecture well in the context of modern agile software teams.
•	Architecture is about the expensive decisions; things that are costly to change later.
•	Ideally architects should code in the production code base. If you are not able to do this at least be involved in quality reviews and peer reviews in the production code so you can get feedback on your designs.
•	It is often said the the code is the only documentation you need but the code can’t tell you everything. You do need to document the things you can’t get from the code such as the architectural drivers, they key quality attributes and so on along with some high level diagrams and how you operate the system.
•	As you step into the role of architect go and find a mentor or a local meet-up. The major change is that you have to influence and lead people.

This podcast is sponsored by AppDynamics. Software architects play a critical role in designi¬¬¬ng, executing, and migrating large infrastructures to the cloud. Download AppDynamic’s FREE eBook “10 Tips for Enterprise Cloud Migration” and launch your migration project with a proven plan. Download the eBook now at http://infoq.link/web_sndcld_appdynamics 


Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2xvq7qM

Show notes

Simon Brown on the Role of the Software Architect in a Continuous Delivery Environment

In a recent episode of the O’Reilly Media Podcast, we spoke with George Miranda about the importance of service mesh technology in creating reliable distributed systems. As discussed in the new report The Service Mesh: Resilient Service-to-Service Communication for Cloud Applications, service mesh technology has emerged as a popular tool for companies looking to build cloud-native applications that are reliable and secure.

During the podcast, we discussed the problems a service mesh infrastructure solves and the service mesh features you’ll find most valuable. We also talked about how to choose the right service mesh for your organization, the challenges involved in getting it deployed to production, and the best ways for getting started with a service mesh.

How to Choose and Deploy a Service Mesh

In this episode of the O’Reilly Media Podcast, Rachel Roumeliotis, VP of content strategy at O’Reilly, sat down with Daniel Krook, IBM developer advocate. They discussed how developers across industries can participate in the Call for Code initiative, the benefits of the program, support from its charitable partners—United Nations Human Rights and the American Red Cross—and the positive impacts IBM hopes to achieve by investing in Call for Code.

Developers Worldwide Will Collaborate on Solutions to Save Lives in Call For Code

This episode of the O’Reilly Podcast, features a conversation on serverless and Kubernetes, with Kelsey Hightower, developer advocate for Google Cloud Platform at Google (and co-author of "Kubernetes: Up and Running"), and Chris Gaun, Kubernetes product marketing manager at Mesosphere.

Kelsey Hightower and Chris Gaun on Serverless and Kubernetes

At Google’s 2019 Cloud Next conference, I sat down with Stephen Thorne, site reliability engineer on Google’s customer reliability engineering team and co-author of "The Site Reliability Workbook," to talk about how organizations, both large and small, can use SRE to reduce operational costs, improve reliability, and create productive cross-functional teams.

How to Get Started With Site Reliability Engineering (SRE)

In this interview, Tim Craig and fellow Googler Gustavo Franco, a site reliability engineer (SRE), discuss the wide range of events that qualify as “incidents;” the need for a conscious, robust, and well-defined process for understanding them; the role of training; and how to get buy-in from management so you can spread incident response training throughout an organization.

Taming Chaos: Preparing for Your Next Incident

O'Reilly Media spreads the knowledge of innovators. At O’Reilly, a big part of our business is paying attention to what’s new and interesting in the world of technology. We have a pretty good record at having anticipated some of the big technology developments in recent history. For instance, we launched the first commercial Web site, GNN, in 1993; we organized the meeting at which the term “open source” was first adopted; we were early investors in Blogger, which helped launch the blogging revolution; and more recently, our Web 2.0 conference launched a world-wide meme. We call this predictive sense the “O’Reilly Radar.” And while we’re certainly not always right, we are, at least, good at making interesting guesses.

Our methodology is simple: we draw from the wisdom of the alpha geeks in our midst, paying attention to what’s interesting to them, amplifying these weak signals, and seeing where they fit into the innovation ecology. Add to that the original research conducted by our Research team, and you start to get a good picture of what the technology world is thinking about.

Understanding Reactive Architecture Through the Actor Model

O'Reilly Radar