Link Dump #234
The sun is shining, the coffee is warm, the weekend is in front of us, and now you also have got something good to read.
The sun is shining, the coffee is warm, the weekend is in front of us, and now you also have got something good to read.
- #BookOfTheMonth
Prompt Engineering for Generative AI - Software Architecture
- Guide to Apache Kafka Disaster Recovery and Multi-Region Architectures #PickOfTheWeek
Managing Kafka across geographic boundaries requires balancing RPO (Recovery Point Objective) and RTO (Recovery Time Objective). This article deep-dives into patterns like Active-Passive and Active-Active setups. Learn how to handle cross-region replication challenges while keeping your stream processing resilient and reliable.
- Guide to Apache Kafka Disaster Recovery and Multi-Region Architectures #PickOfTheWeek
- Software Development
- Security as Code is Becoming the New Baseline: Continuous Compliance in DevOps
Explore how Continuous Compliance replaces manual gates with automated verification. Discover the shift from 'Security as a Gate' to 'Security as a Service,' where developers get instant feedback and security teams become policy engineers. - Why Environment Architecture Matters More Than Ever for AI Readiness #PickOfTheWeek
AI agents don't have intuition or patience. If they can't figure out how to run your tests in 10 seconds, they fail. The author argues that 'Good Environment Architecture' is the new prerequisite for AI readiness. Discover how to build a system that explains itself through intentional layout and reliable scripts. - One tip for successful OpenTelemetry projects
The best way to introduce OpenTelemetry is by targeting "low-hanging fruit." Nicolas Fränkel argues for a zero-code-change approach, using scrapers to collect metrics from existing interfaces rather than refactoring. - The one where Oskar explains Example Mapping #PickOfTheWeek
Introduction to Example Mapping explains how to turn vague requirements into executable specifications. By focusing on concrete examples rather than abstract discussions, teams can eliminate ambiguity and create a shared understanding in record time. If your refinement sessions feel like aimless debates, this simple card-based framework is the antidote you need. - Encoding Team Standards #PickOfTheWeek
This article details practical methods for embedding team norms - from naming conventions to architectural patterns - directly into AI prompts and tools. Learn how to automate the "boring" parts of code review and ensure consistency across your entire organization without manual micromanagement.
- Security as Code is Becoming the New Baseline: Continuous Compliance in DevOps
- Code Quality
- Dealing with Technical Debt
Why does technical debt always lose to new features? Because it’s invisible. This deep dive into Continuous Technical Debt Management explains how to build a Unified Backlog that puts Features, Defects, and Debt on the same playing field. - Stop Using Pull Requests #PickOfTheWeek
Designed for untrusted contributors, the PR model is often a poor fit for professional teams, creating an expensive bottleneck. This article makes a compelling case for higher-bandwidth collaboration, like trunk-based development, to reduce lead times and eliminate superficial reviews.
- Dealing with Technical Debt
- Leadership
- The Destruction of “Maybe”
Leaders often use "maybe" to avoid conflict or keep options open, but the result is organizational paralysis. Learn why a wrong decision is often better than no decision at all, and how to master the art of the definitive answer to keep your projects moving forward.
- The Destruction of “Maybe”
- Fun
Comments ()