InfoQ Homepage Stories & Case Studies Content on InfoQ
-
Hard-Won Lessons from the Trenches: Failure Modes of Platform Engineering — and How to Avoid Them
Platform Engineering is a hot topic with many orgs hoping to reap the benefits. However, it is easy to go astray. This article reviews the common pitfalls of building a platform and how to avoid them.
-
How to Measure the Energy Consumption of Bugs
Software engineers should accept their responsibility for taking energy consumption and carbon dioxide emissions into account when developing software; they have a big responsibility towards nature, our environment and sustainability. This article sheds light on how software engineers can this perspective into account, zooming in on energetic shortcomings or bottlenecks of bugs.
-
How Behaviour-Driven Development Helps Those with Sleep Disorders Contribute Effectively
Invisible illnesses, including sleep disorders, are prevalent in the workplace. Teams that are open and accepting of those with sleep disorders benefit in their planning accuracy and quality practice from diverse viewpoints. An open and welcoming team culture plays a large part in helping team members overcome challenges.
-
Software Testing through the Lens of Energy Management
I’m a software tester who observed that certain activities were getting me excited, while other simpler, shorter activities were draining and took a lot longer to get me motivated enough to even pick them up . This article is an experience report of how I discovered my personal energy system and superimposed it on a video game model, which also applies to the world of software testing.
-
Enabling Effective Remote Working - Principles and Patterns from Team Topologies
This article shares ideas, principles, and practices from Team Topologies (and related topics) to help organizations approach their structures' design and evolution to better support interactions in remote working. It also shares examples to showcase their impact when used to better approach organizational design, in general, and particularly to support remote working.
-
Craftleadership: Craft Your Leadership as Developers Craft Code
Learning software craftership made me reconsider how I wrote code. Being an experienced software team manager, I try to reevaluate my management practices in the same way: what could test-driven management or pair-management be? Here I propose different insights on how software craftership tools and mindset are transposable to the management domain.
-
From Async Code Reviews to Co-Creation Patterns
This article dives into the throughput and quality of the async code review process, which are very important dimensions to optimize for in product development teams. It also explains why co-creation patterns – Pair and Mob programming – as an alternative way of working are able to optimize for both of those dimensions, instead of needing to trade off between them.
-
How We Built Testability with Psychological Safety
Testability can enable teams to make changes to their code bases without requiring extensive regression testing. To build testability, team members must collaborate and leverage each other's unique skills. Unfortunately, effective collaboration does not come naturally to people and therefore needs leadership to nurture people's ability to speak up and share their knowledge.
-
Why is Everything So Slow? Measuring and Optimising How Engineering Teams Deliver
As teams grow, they will slow down, but it should not mean that teams stop delivering value that can power future business growth. Avoiding excessive technical debt and ensuring systems are secure and performant becomes increasingly important. As an engineering leader, you can do things to be confident that your team is moving at the fastest and most sustainable pace.
-
Accessing Agile Games as a Tool in Transformation and Change
This article puts the usage of Agile Games into a broader business context and introduces the steps needed to make any game a verifiable contribution to a given business objective. As “business” is a wide area of topics to be addressed, the article focuses on accessing Agile Games as a tool used within transformation and change. It provides an example that was taken from this area.
-
DevOps at Schneider: a Meaningful Journey of Engaging People into Change
Adopting DevOps at Schneider started with building a case for change. Tech people were engaged into change by organizing learning and collaboration sessions and getting feedback from the front lines. Change is hard and without leadership support, dedicated time for developers to really digest it and continual reinforcement and conversation, it will be challenging to be successful.
-
How Development Teams Can Orchestrate Their Workflow with Pipelines as Code
Infrastructure as Code was just the beginning. Configuration as Code followed shortly after – again becoming extremely commonplace and enabling organisations to scale their engineering capacity by a number of times. And in order to continuously increase the value development teams generate, Pipelines as Code is the natural consequence.