Link Dump #236

Why do I like AI? One of the reasons is - it "buys" me more time for micro-reading:

1. Software Architecture
   1. Anti-patterns in event modelling - Passive-Aggressive Events #PickOfTheWeek
      The author explores a common EDA anti-pattern where producers "announce" facts while secretly expecting a specific reaction. This "passive-aggressive" style creates hidden coupling and blocks workflows. Learn how to identify when your events are lying to you and why making commands explicit is the key to true component autonomy.
2. Software Development
   1. Agentic CI/CD is Not Automation: Why the Distinction Will Define DevOps in 2026
      This article breaks down why agentic systems require a new operational contract: semantic constraints, decision-based audit trails, and confidence-threshold circuit breakers. It’s a roadmap for shifting from deterministic scripts to probabilistic systems without sacrificing SLOs or security.
   2. The Ultimate Quesstion: What Does the Endgame Look Like? #PickOfTheWeek 
      Everyone are saying that in X months/years Y will happen thanks to/because of the AI. The author goes beyond hype-driven predictions and by validating what constraints will have an impact on how the endgame may look like.
3. Leadership
   1. 7 tests to expose wise leaders
      This article explores how to identify wisdom through curiosity, consistent conduct, and the growth of others. If you want to know if a leader is truly worth following, look at who influences them and whether their presence instructs or merely commands. 
   2. Why Smart Teams Overcommit And How Leaders Make It Worse #PickOfTheWeek
      The author explains why smart teams are actually more prone to overcommitting due to the "planning fallacy." Discover how to break the cycle of over-optimism and why building "slack" into your sprint is a sign of maturity, not laziness.
   3. Should You Develop Your Leadership Strengths—or Fix Your Weaknesses?
      Leaders shouldn’t automatically choose between building strengths or fixing weaknesses. Instead, they should diagnose what their situation requires by asking questions: What does success require in my role? What are my current capabilities? What is already compensated for? Where is my untapped potential?
4. Fun
   1. User Stories for Clarity