InfoQ Homepage Business Content on InfoQ
-
The Challenge of Cognitive Load in Platform Engineering: a Discussion with Paula Kennedy
In a recent article, Paula Kennedy shared her thoughts on the ever-increasing cognitive load being saddled onto development teams. Although platform engineering is touted as a solution to this challenge, a poorly designed platform will increase the cognitive burden on developers utilizing it. We must also be careful that we are not just transferring that cognitive load onto the platform teams.
-
The Future of DevOps is No-Code
The need for high-quality DevOps personnel is skyrocketing, but it is harder than ever to find enough staff. It is possible to augment your DevOps organization using no-code and low-code tooling. Low-code and no-code tools can free up existing developers by reducing the time spent on integrating and administering DevOps toolsets.
-
Successfully Integrating Dynamic Security Testing into Your CI/CD Pipeline
Dynamic security testing tools don’t require advanced cybersecurity knowledge to operate. Integrating DAST into your CI/CD pipeline should be done in stages by focusing on the riskiest areas first.
-
Hidden Habits Killing Your Remote Team’s Ability to Collaborate Effectively
Some habits carried over from in-person work continue to damage collaboration and engagement for hybrid and remote teams. By not addressing these habits, teams are experiencing deteriorating morale, lack of trust and connection required for meaningful collaboration. Here are four examples of habits leaders can address today to build more connected, engaged and innovative teams.
-
Choosing the Right Cloud Infrastructure for Your SaaS Start-up
As a solutions architect, I have been designing SaaS applications for years and I have seen start-ups struggle to find the right cloud infrastructure and improve their product offering. These experiences prompted me to write this article as a tool to help companies make a pragmatic fact and data-driven decision.
-
Building Workflows with AWS Step Functions
AWS Step Functions use a state machine to represent the workflow. A workflow consists of a set of tasks, each of which represents a discrete activity to be performed. Each task is defined by a state of the state machine. In this article, we will learn about the main concepts of AWS Step Functions and apply those to build a workflow for a sample business process: Order Fulfillment.
-
The Implication of Feedback Loops for Value Streams
Lead time and throughput are dynamic variables which impact flow in a value stream. Capacity, processing time and feedback loops (such as error conditions) have a significant impact on WIP and flow and need to be mapped and measured when building value stream maps.
-
Business Systems Integration is about to Get a Whole Lot Easier
A new breed of integration software is arising that syncs business data into a simplified data hub and then syncs that data to the destination system. The benefit of this integration pattern is that it reduces the number of manual transformations required (often to zero) and makes it easier to write manual transformations when you have to.
-
The IT Leader’s Guide to Helping Developers Avoid Burnout
The developer workforce has become increasingly distributed over the past two-plus years, contributing to new levels of stress. There are things IT can help leaders do to prepare for the future of software development, yet still ensure their teams have the tools and resources they need to keep individuals engaged, motivated, and fulfilled by their work.
-
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.
-
DevOps and Cloud InfoQ Trends Report – June 2022
This article summarizes how we see the "cloud computing and DevOps" space in 2022, which focuses on fundamental infrastructure and operational patterns, the realization of patterns in technology frameworks, and the design processes and skills that a software architect or engineer must cultivate.
-
Why the Dual Operating Model Impedes Enterprise Agility
Most organizations adopt a dual approach to agility, with some parts of the organization working in an agile way that delivers value in increments, measures the response and adapts accordingly, while the “traditional” organization continues to work as it always has in a relatively top-down way. In this article, This approach must eventually be left behind after an Agile transition.