InfoQ Homepage Business Content on InfoQ
-
Platform Engineering Needs a Prescriptive Roadmap: a Conversation with Nigel Kersten
Nigel Kersten feels that it is time for a prescriptive roadmap for how to adopt and implement platform engineering. A lack of definition for DevOps enabled early adopters but didn't allow late-majority enterprises to be successful in their adoption of DevOps. The platform engineering community is in danger of repeating this mistake.
-
The Future of Technology Depends on the Talent to Run it
Effective nearshore staff augmentation—a savvier form of outsourcing—allows organizations to bypass the skills gap and mitigate turnover. Nearshoring can help companies build great teams of professionals who are located in the same time zone, charge reasonable rates, and collaborate directly with in-house teams.
-
Great Leaders Manage Complexity with Self-Awareness and Context Awareness
People's perception and expectations on leadership requires a leader to understand their own contextual significance which makes it difficult to become an appreciated leader. Also trivialisation many times unknowingly stands in the way of progress in complex situations. This article explores specific traits that distinguish people who repeatedly provide appreciated and appropriate leadership.
-
Adopting Low Code/No Code: Six Fitnesses to Look for
When selecting a no-code/low-code platform, six key fitnesses should be examined: purpose fit, cost fit, ops fit, user fit, use-case fit, and organization fit. The IT team should be heavily involved in this decision as they play a pivotal role in helping citizen developers with platform adoption.
-
Extinguishing IT Team Burnout through Mindfulness and Unstructured Time
Burnout is taking a toll on IT and creating serious skill shortages. How can you keep your IT team engaged, productive, and happy? Mindfulness and unstructured time are delivering tangible business benefits that positively impact the bottom line, all while driving worker satisfaction and well-being.
-
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.