InfoQ Homepage Conferences Content on InfoQ
-
Understanding Architectures for Multi-Region Data Residency
This article focuses on implementing data residency strategies for a positive stakeholder experience. It underscores the need to diversify data locations, driven by motivations like disaster recovery and geo-redundancy. The core principle is data distribution, ensuring specific sets reside in distinct regions without overlap - a practice termed data residency.
-
How to Deal with Complexity in Product Development by Using Solution-Focused Coaching
In this article, you will discover how and which parts of coaching and nuanced language can help you leverage your interactions to yield better results in product management. Integrating specific coaching principles can enhance the quality of your conversations by guiding dialogue to uncover actionable insights, foster trust, boost collaboration, and drive clarity in your objectives.
-
Generative AI and Organizational Resilience
Generative AI will profoundly transform communication and information sharing over the next decade, but the change will be uneven across industries and roles. Organizations should empower workers to use AI augmentation thoughtfully, while building literacy on capabilities and limits. A balanced, conscientious integration, using iterations and customer feedback, will produce the best outcomes.
-
Orchestrating Resilience Building Modern Asynchronous Systems
In this article, we will discuss what problems we had to solve at Twilio to efficiently build a resilient and scalable asynchronous system to handle a complex workflow and the advantages we got from adopting a Workflow Orchestration solution, including abstracting away state management and out-of-the-box support for retries, observability, and audibility.
-
The Incident Lifecycle: How a Culture of Resilience Can Help You Accomplish Your Goals
Don’t get stuck with overwhelmed systems that can cause an outage, like what happened with Taylor Swift concert tickets. Build organizational resilience to incidents through improved coordination and communication during the response, and blameless reviews, root cause analysis, and insightful communication afterward to enable meaningful change.
-
Tips on How Staff Engineers Can Impact Incidents
Staff engineers can influence behaviors during and after incidents by modeling transparency and questioning assumptions to strengthen engineering culture. As incident commanders, they can coordinate workstreams, communicate with stakeholders, and prevent responder burnout. In retrospectives, staff engineers can improve model root cause analysis to improve underlying cultural issues.
-
Write More, Talk Less: Building Organizational Resilience through Documentation and InnerSource
Better documentation and knowledge sharing creates transparency that aids onboarding, prevents turnover disruption, and withstands reorganizations. Different practices can help, such as communicating asynchronously, creating incentives for documentation, making docs discoverable, understanding team members' preferences, and providing dedicated writing time. And maybe InnerSource can help too.
-
Agile Coaching as a Path toward a Deeper Meaning of Work and Life
In this article, we take a deeper look at the practice and purpose of agile coaching. We find out why interactions are the most essential focus in agile coaching - and also the basis of learning and professional development for the agile coaches themselves. We also learn how focusing on our existing strengths and situations can help us discover our authentic purpose in work and life.
-
Agile Rehab: Replacing Process Dogma with Engineering to Achieve True Agility
Struggling with your "agile transformation?" Is your scaling framework not providing the outcomes you hoped for? In this article, we’ll discuss how teams in a large enterprise replaced heavy agile processes with Conway’s Law and better engineering to migrate from quarterly to daily value delivery to the end users.
-
How Agile Teams Can Improve Predictability by Measuring Stability
In this article, we will present our approach for analysing agile systems as networks of queues and how we have used it to analyse 926 projects in the Public Jira Dataset. We explain how you can measure the Stability Metric (SM) for your queues. Finally, we will present our planned next phase of research.
-
Bridging Silos and Overcoming Collaboration Antipatterns in Multidisciplinary Organisations
There's a worrying trend towards focusing on specialisms at the expense of collaboration, shared responsibility and valuable outcomes, which can take teams away from multi-disciplinary collaboration. This article calls out three collaboration anti-patterns that appeared in more than one organisation, some of the symptoms they cause and some thoughts on how to go about counteracting them.
-
Why Developers and Staff+ Engineers Should Get Involved in Open-Source Collaborative Development
Over the last 30 years, the world has become connected and digital. Open source is how we do modern software development, stitching together downloaded open-source libraries, frameworks, and other code to create new applications or functionality. This is why every developer and senior staff+ roles need to know what open source is and how it works.