InfoQ Homepage Articles
-
How to Seamlessly Evolve DevOps into DevSecOps
As DevOps evolved, it became obvious that it was about more than just software development and operations management. With each new story of a massive data breach and its catastrophic consequences, cybersecurity swiftly became recognized as a critical part of any IT ecosystem. This realization led to DevSecOps. This article looks at how to embrace a DevSecOps approach.
-
Q&A on A Scrum Book: The Spirit of the Game
In A Scrum Book: The Spirit of the Game, Jeff Sutherland and James Coplien explore how to do Scrum well using patterns. There are more than ninety patterns which provide insight into Scrum’s building blocks, how they work, and how highly effective teams use them.
-
It Ain't Necessarily So: Exploring Type Systems for Verifying Musical Correctness
Chris Ford explores what makes music correct and how we might encode it in a type system.
-
NotPetya Retrospective
As we hit the second anniversary of NotPetya, this retrospective is based on the author’s personal involvement in the post-incident activities. In the immediate aftermath, it seemed like NotPetya could be the incident that would change the whole IT industry, but it wasn’t—pretty much all the lessons learned have been ignored.
-
Q&A on the Book Empathy at Work
The book Empathy at Work by Sharon Steed explores the role empathy plays in team communication and interaction, and provides tools to help people become better empaths in difficult situations. It describes the steps we can take in order to show empathy daily and contribute to a healthy, collaborative, positive work culture.
-
Power to the People: Unleashing Teams through Liberating Structures
Liberating Structures are a great way for teams to find their voice. They make this happen by asking us to think creatively about the kinds of invitations we are making, and by subverting the normal power dynamics in a meeting. In this article, Greg Myer shares how he is using Liberating Structures at Capital One.
-
Obscuring Complexity
One of the most important things that software architects do is manage the complexity of their systems in order to mitigate release disruption while maintaining sufficient feature velocity. When we cannot reduce complexity, we try to hide or shift it. Software architects tend to manage that complexity with the time-honored strategies covered in this article.
-
The Importance of Metrics to Agile Teams
This article outlines the importance of and proposes meaningful Agile metrics for teams seeking to raise overall performance and whose members seek to continuously self-improve. It emphasizes that team members should democratically agree and manage these metrics. It also advises what to look for in tools that track performance against agreed metrics over time.
-
Using OpenAPI to Build Smart APIs for Dumb Machines
This article discusses how to build, manage and maintain APIs with OpenAPI, including some of the most notable features in v. 3.0.
-
How to Use Open Source Prometheus to Monitor Applications at Scale
In this article, the author discusses how to collect metrics and achieve anomaly detection from streaming data using Prometheus, Apache Kafka and Apache Cassandra technologies.
-
Q&A on the Book Risk-First Software Development
The book Risk-First Software Development by Rob Moffat views all of the activities on a software project through the lens of managing risk. It introduces a pattern language to classify different risks, provides suggestions for balancing risks, and explores how software methodologies view risks.
-
Five Android and iOS UI Design Guidelines for React Native
This article will explain why UI designers should follow platform specific guidelines while designing for multiple platforms. This can be quite a complex task, due to the variety of constraints and guidelines there are to consider. We propose five easy guidelines to design for multiple platforms focusing on React Native and without missing key usability concerns.