Most video game designers dream of designing a blockbuster hit, but what makes a game break out?
Find out what pays and what doesn't for software engineers, developers, and other programming professionals.
Get practical knowledge on the advantages microservices can bring to your project.
Five must-haves for robust, debuggable production code.
Jessica Kerr says one of the hardest problems in software is software.
Daniel Krook explores Apache OpenWhisk on IBM Bluemix.
Matt Stine explains how patterns can help us make sense of the ongoing paradigm shift in software architecture.
As designers of systems, Aaron Bedra says it is your responsibility to ensure that security is built in.
Watch highlights covering microservices, distributed systems, security, and more. From the O'Reilly Software Architecture Conference in New York 2017.
Mark Richards offers a glimpse of what software architecture will look like in the future, and he shares the things software architects will need to focus on in the years ahead.
Bridget Kromhout says designing distributed systems means considering failure scenarios—both likely and less so.
Mike Roberts introduces the concepts behind serverless architectures and provides reasons why it's worthy of some of the hype it’s receiving.
An architectural overview of an image processing example.
Apply modular system design principles while avoiding the operational complexity of microservices.
How to cultivate lasting shared knowledge without giving up all that free time you don't really have.
Spend more time building and less time fixing with GitHub Pull Requests for proper code review.
Get practical knowledge on why and how to port your project to Python 3.
It makes no sense at all for programming to be stuck on laptops, but that's where we are.
Learn how to handle array comparisons using the set_intersection algorithm in C++.
The O’Reilly Hardware Podcast: Powering connected devices with low-power networks.
Containers helps you distribute, deploy, run, and test your Golang projects.
Toward a virtuous cycle between people, devices, and cloud.
Learn how to enable functional behavior in Scala code.
Create business value and add new functionality through an automated build pipeline.
A look into the unspoken side of software architecture.
An interview with Susan Fowler, Site Reliability Engineer at Uber Technologies.
Communication skills make or break the effectiveness of a developer.
From "Linux is a cancer" to Windows Subsystem for Linux.
An interview with Martin Thompson, High-Performance Computing Specialist at Real Logic.
The O’Reilly Hardware Podcast: An all-in-one workshop factory.
What will innovations like dynamic plugins, serverless Go, and HTTP/2 Push mean for your development this year?
An improved asyncio module, Pyjion for speed, and moving to Python 3 will make for a rich Python ecosystem.
Mike Roberts, Co-founder at Symphonia, on how serverless came about, where it's being used, and what lies ahead.
Open source development, changing infrastructure, machine learning, and customer-first design meet in a perfect storm to shape the next massive digital transformation.
An interview with Scott Shaw, Head of Technology, Australia, at ThoughtWorks.
An interview with Dianne Marsh, Director of Engineering, Cloud Tools, at Netflix.
The O’Reilly Hardware Podcast: Making hardware programmable.
Making a lasting impact with microservices takes more than a change in technology.
Landing on a set of simple reactive design principles in a sea of constant confusion and overloaded expectations.
Learn about Swift’s most impactful and interesting new features, and explore Swift’s use on non-Apple platforms.
Watch highlights covering software architecture, microservices, distributed systems, and more. From the O'Reilly Software Architecture Conference in San Francisco 2016.
Rachel Laycock and Cassandra Shum take opposing sides in the microservices debate.
Kelsey Hightower offers a quick overview of Kubernetes—the community, the project, and the technology for managing containerized workloads.
Martin Thompson explores the architectures that emerge from applying design patterns required for high performance, resilience, security, usability, and other quality-of-services measures.
The O’Reilly Podcast: Hugh McKee on learning how to think asynchronously to create highly concurrent business systems.
Regular expressions are the standard for string processing, but did you know you can often get better text untangling with Pynini's finite-state transducers?
Faced with business and regulatory complexity, Scott Shaw found himself committing some of the software development acts he once condemned. He confesses those sins and explains why they’re sometimes necessary.
Mike Roberts introduces the concepts behind serverless architectures, explains how serverless breaks from the past, and provides reasons why it's worthy of some of the hype it’s currently receiving.
Dianne Marsh explains how microservices paved the way for traffic steering at Netflix, and she highlights current challenges.
The O'Reilly Hardware Podcast: Qubits and the future of computing.
Exploring the many trends in business, education, and government that have contributed to the current state of open source activity in Brazil.
Watch highlights covering software architecture, microservices, distributed systems, and more. From the O'Reilly Software Architecture Conference in London 2016.
Balancing optimization efforts across processes, technologies, and teams.
Rob Harrop looks at how we can use the concepts of CSP, Actors, and Reactive as powerful tools for reasoning about our systems.
Patrick Kua explores why and how software architects should care about high-performance teams.
Kevlin Henney explains how uncertainty, lack of knowledge, and options can be used to drive a system’s architecture and its development schedule.
Greg Brown's new book, Programming Beyond Practices, is a thoughtful exploration of how software gets developed.
Taking opposing sides, Rachel Laycock and Cassie Shum debate the merits of microservices.
Martin Thompson explores emergent designs and working practices that succeed in areas where the design pressures quickly cull that which does not deliver.
Mark Richards discusses the factors that have enabled the evolution of software architecture over the past three decades and explores what the future of software architecture might look like.