InfoQ Homepage Culture & Methods Content on InfoQ
-
/articles/managing-technical-debt-microservices/en/smallimage/logo-1643626223282.jpg)
Managing Technical Debt in a Microservice Architecture
At QCon Plus, Glenn Engstrand described how Optum Digital engineering devised a method for reliably and predictably paying down tech debt for hundreds of microservices, forming relevant communities and identifying high-risk areas. The communities' collective decisions can be compiled into an actionable roadmap and presented to product managers in a systemic and non-confrontational way.
-
/articles/better-metrics-team-performance/en/smallimage/logo-1643374520292.jpg)
Better Metrics for Building High Performance Teams
There is no agreed way to build and measure high performing engineering teams, let alone to track the success of software engineers. This article explores ways to support individuals and teams right from onboarding and identifies useful metrics which can help make performance factors visible and actionable. Developer onboarding, dynamic documentation, and asynchronous communication are key.
-
/articles/financial-times-engineering-enablement/en/smallimage/enabling-engineering-productivity-at-the-financial-times-small-1643105626728.jpg)
How the Financial Times Approaches Engineering Enablement
Companies need teams working on infrastructure, tooling and platforms; the way they work has to change so that they do not become a bottleneck. These teams need to be about enabling product teams to deliver business value. Investment in this area pays off as it speeds up many other teams and allows product-team engineers to focus on solving business problems that provide value to the organisation.
-
/articles/hybrid-remote-2022/en/smallimage/logo-1642153435805.jpg)
Hybrid & Remote Work in 2022 and Beyond
Moving into 2022, ways of working and interacting are continuing to evolve as organisations adapt to the ongoing changes brought about by a wide range of factors influenced by the COVID-19 pandemic. Making remote work sustainable, flexible, hybrid and asynchronous working, recognising the importance of employee experience and supporting mental wellness are important trends in the future of work.
-
/articles/summary-podcast-2021-review/en/smallimage/InfoQ-Trend-Report-logo-1642446751680.jpg)
The Major Software Industry Trends from 2021 and What to Watch in 2022
In this podcast summary Thomas Betts, Wes Reisz, Shane Hastie, Charles Humble, Srini Penchikala, and Daniel Bryant discuss what they have seen in 2021 and speculate a little on what they hope to see in 2022. Topics explored included: hybrid working and the importance of ethics and sustainability within technology.
-
/articles/create-psychological-safety-teams/en/smallimage/logo-s-1642181873131.jpg)
Creating Psychological Safety in Your Teams
Psychological safety is a work climate where employees feel free to express their questions, concerns, ideas and mistakes. We cannot have high-performing teams without psychological safety. In this article, you will learn practical ideas, interesting stories, and powerful approaches to boost psychological safety in your team.
-
/articles/insider-security-threats-zero-trust/en/smallimage/logo-1641193907181.jpg)
Mitigating Inside and Outside Threats with Zero Trust Security
As ransomware and phishing attacks increase, it is evident that attack vectors can be found on the inside in abundance. Zero Trust Security can be thought of as a new security architecture approach where the main goals are: verifying endpoints before any network communications take place, giving least privilege to endpoints, and continuously evaluating the endpoints throughout the communication.
-
/articles/waste-impediments-data-science/en/smallimage/logo-1641428353252.jpg)
Getting Rid of Wastes and Impediments in Software Development Using Data Science
This article presents how to use data science to detect wastes and impediments, and concepts and related information that help teams to figure out the root cause of impediments they struggle to get rid of. The knowledge discovered during research includes an expanded waste classification, and the use of trends to uncover undesired situations like hidden delayed backlog items and defects trends.
-
/articles/spaces-shape-collaboration-anthropology/en/smallimage/how-space-shapes-collaboration-small-image-1640183715486.jpg)
How Space Shapes Collaboration: Using Anthropology to Break Silos
Software companies strive to keep innovating and changing the rules of the market. These companies are made of people who, unlike smartphones, personal computers or smart watches, have not evolved as much in recent years. This article proposes an analysis of workspaces from anthropology to solve one of the most common problems: the appearance of silos instead of a culture of collaboration.
-
/articles/avoiding-technical-bankruptcy/en/smallimage/avoiding-technical-bankruptcy-small-image-1640173923994.jpg)
Avoiding Technical Bankruptcy: a Whole-Organization Perspective on Technical Debt
Technical debt is not primarily caused by clumsy programming, and hence we cannot hope to fix it by more skilled programming alone. Rather, technical debt is a third-order effect of poor communication. What we observe and label “technical debt” is the by-product of a dysfunctional process. To fix the problem of accumulating technical debt, we need to fix this broken process.
-
/articles/remote-ensemble-working-experiment/en/smallimage/logo-1640103875374.jpg)
Remote Ensemble Testing - How an Experiment Shaped the Way We Work
This article shares how an experiment evolved into a common practice at the workplace, using an experimental approach with remote ensemble testing to get teammates on our cross-functional team more involved in the testing activities of the jointly created product. This all started in the times of a global pandemic where the entire team was working from home.
-
/articles/measure-outcomes-not-outputs/en/smallimage/measure-outcomes-not-outputs-small-1639490155013.jpg)
Measure Outcomes, Not Outputs: Software Development in Today’s Remote Work World
Today’s remote work world calls for a closer look at how to measure software developer productivity. Currently, there is no standard metric and widely used methods are flawed. The author describes how they successfully lead 500+ remote software developers by measuring outcomes, rather than outputs in order to produce the ideal balance between speed and quality code development.