InfoQ Homepage Articles
-
/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/deep-learning-institutional-incremental-learning/en/smallimage/institutional-incremental-learning-small-image-v2-1640874831613.jpg)
Developing Deep Learning Systems Using Institutional Incremental Learning
Institutional incremental learning promises to achieve collaborative learning. This form of learning can address data sharing and security issues, without bringing in the complexities of federated learning. This article talks about practical approaches which help in building an object detection system.
-
/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/uber-deployment-planet-scale/en/smallimage/safe-and-fast-deploys-at-planet-scale-small-image-1639566319120.jpg)
Safe and Fast Deploys at Planet Scale
At QCon Plus, Mathias Schwarz, a software engineer at Uber, presented safe and fast deploys at planet scale. Uber is a big business and has several different products. They are, in most cases, deployed to dozens or hundreds of markets all over the world.
-
/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.
-
/articles/six-features-jdk12-to-jdk17/en/smallimage/six-features-from-Java-12-to-17-to-get-excited-about-small-1639487914685.jpg)
Six Features From Java 12 to 17 to Get Excited About!
Oracle maintains an ambitious release schedule for new versions of Java, having one fixed release every six months. Although frequent, only some versions are considered long-term support, which means they’ll have premium maintenance for three years. In this article, I review some of the language additions between Java 12 and 17, for anyone interested in what’s been happening since Java 11.
-
/articles/experiment-driven-quality-culture/en/smallimage/logo-1639487261025.jpg)
Growing an Experiment-Driven Quality Culture in Software Development
Have you ever faced a challenge at work that you weren’t sure how to tackle? Experiments to the rescue! In a complex environment like software development, no one can tell what might work, so we have to try things out. Read this article to learn about key challenges, insights and lessons, and get inspired for your own path to experimentation.
-
/articles/getting-started-grpc-dotnet/en/smallimage/logo-1638894843213.jpg)
Getting Started with gRPC and .NET
In this article, the author introduces the core concepts behind gRPC and how it can be used with API development. The basic pros and cons of using gRPC instead of REST are also explained with a scenario analysis. The text is illustrated with a step-by-step tutorial on how to use gRPC to develop streaming services in .NET.
-
/articles/saas-drbc-data-backup/en/smallimage/logo-1638816590039.jpg)
SaaS DR/BC: If You Think Cloud Data is Forever, Think Again
SaaS is quickly becoming the default tool for how we build and scale businesses. It’s cheaper and faster than ever before. However, this reliance on SaaS comes with the risk of disaster recovery. The “Shared Responsibility Model” doesn’t just govern your relationship with cloud, it actually impacts all of cloud computing. Even for SaaS, users are on the hook for protecting their own data.
-
/articles/data-application-process/en/smallimage/logo-1638797109490.jpg)
You’re Doing it Wrong: it’s Not about Data and Applications – It’s about Processes
Classic developer thinking tends to approach application design from a data-centric point of view. When the domain is process management, that often leads to excess complexity and work; it also (wrongly) over-reduces proactive processes to quick bursts of automation triggered by data changes. There’s a better way to do this: start with the process.