InfoQ Homepage Technical Excellence Content on InfoQ
Articles
RSS Feed-
How Psychological Safety at Work Creates Effective Software Tech Teams That Learn and Grow
This article provides the foundations of psychological safety and shows how it has been applied for team effectiveness. It explores how psychological safety supports learning and improvement and how we can foster a psychologically safe culture in tech teams.
-
Technical Debt Isn't Technical: What Companies Can Do to Reduce Technical Debt
In this article, three experts discuss some of the key findings of the “State of Technical Debt 2021” report including the impact of technical debt on engineering teams, the pros and cons of dealing with maintenance work continuously, the future of technical debt and what each engineering teams can do to communicate the importance of dealing with technical debt to companies’ leadership.
-
Signs You’re in a Death Spiral (and How to Turn It around before It’s Too Late)
Don’t let feature work blind you. Enterprises are ramping up their software delivery to compete in the digital-first world. But more features and faster time-to-market can lead your business into a death spiral if you neglect technical debt and risk work. Learn how to use value stream metrics to identify whether your business is in danger and how to reverse the trajectory before it’s too late.
-
Q&A on the Book Agile Machine Learning
The book Agile Machine Learning by Eric Carter and Matthew Hurst describes how the guiding principles of the Agile Manifesto have been used by machine learning teams in data projects. It explores how to apply agile practices for dealing with the unknowns of data and inferencing systems, using metrics as the customer.
-
Simplicity, Please - A Manifesto for Software Development
An unrelenting and breathless rush to market is quietly driving your company to the brink of extinction. Maybe it’s time to rethink how you design and write code. Investment in simplicity is investment in speed. Simplicity is also the mother lode of intellectual property — and a competitive advantage almost impossible to regain once lost.
-
How to Sell Refactoring? The Case of Nordea Bank AB
Refactoring is often not a technical challenge. Teams can accurately diagnose inefficient code design. If they have sufficient time and budget at their disposal, they would probably get things done. In this article, we focus on the strategic code refactoring. This distinction was introduced by the BNS IT consultants as part of the method called Natural Course of Refactoring.