Writing about how the things that look good in the book actually work in the field.
Notes on Scrum ceremonies, team leadership and software engineering. Every post follows the same skeleton: what it is for → how it should work → how it breaks → checklist. Practice, not theory.
Scrum and Process
The ceremonies are a chain: broken refinement makes planning drag, broken planning turns the daily into a status report. That is why these are written to be read in order.
Being Agile vs Doing Scrum
Agile does not end the chaos; it makes it visible. That is why teams can run every ceremony and still not be agile.
PART 02Backlog Refinement: Kill Bad Ideas Early
Refinement is a funnel, not a meeting. Back-of-the-envelope filtering and ROI in one shared currency.
PART 03Grooming: Not a Ticket Reading Session
The PO's job is not to read out what will be built, but to explain why it matters.
PART 04Sprint Planning: Commitment, Not Estimation
Good planning is boring. If surprises show up, the preparation failed. Capacity math and the pull system.
PART 05Daily Standup: Synchronization, Not a Status Report
If what you did yesterday does not affect today, it does not matter. Walking the board, and the async option.
PART 06Sprint Review: A Feedback Loop, Not a Demo Show
If nobody objects, nobody is listening. Silence is the worst signal.
PART 07Retrospective: Tracked Actions, Not Wishes
Definition, owner, deadline — without all three it is a wish, not an action.
PART 08Epic, Story, Task: How to Break Work Down
Why should a task never exceed one day? Six ways to cut work, walked through a real e-commerce returns project.
PART 09Does Scrum Make Customers Happy?
Bringing the customer inside: from 1 project to 9, from 1 person to a team of 14. A real story from the field.
Team Leadership
The human side rather than the process: hard conversations, performance, what replaced authority, and what a manager is actually for in the age of AI.
How to Give Negative Feedback
Why does the sandwich fail? The event → impact → expectation pattern, with real dialogue.
LEADERSHIPCan You Measure Performance With OKRs?
Tie a bonus to a target and people shrink the target. Why story points inflate, and what to read instead.
LEADERSHIPNew-Generation Leadership: Authority Is Gone, Now What?
The information monopoly ended, dependence ended. What replaced them, and the power of "I do not know".
LEADERSHIPAI or Leadership?
Writing got cheap, verifying got expensive. The junior learning path and the leader's changed job.
LEADERSHIPSquad, Tribe, Chapter, Guild: Choosing an Org Model in One Week
The first target handed to me in a meeting with the CEO. 52 conversations, a one-sentence diagnosis, and what we left out of the Spotify model.
LEADERSHIPOne-on-Ones: An Early Warning System, Not a Status Meeting
Thirty minutes a week, and the agenda is theirs. Why "how is it going?" always returns "fine", and what to ask instead.
LEADERSHIPDeveloper to Manager: A Career Change, Not a Promotion
Promoting your best engineer can lose you twice. The right measure for how much code to keep writing.
LEADERSHIPDelegation: Letting Go of the Outcome, Not Handing Out Tasks
Hand work over and then hover, and you have not delegated. Authority with responsibility, and the ten-minute trap.
LEADERSHIPPsychological Safety: Measurable Behaviour, Not Good Intentions
Saying "speak freely" does not do it. Who speaks first, how late bad news arrives, and how incident reviews kill it.
LEADERSHIPConflict: Surface It, Don't Suppress It
Two seniors disagree on architecture and the team picks sides. Separating ideas from people, and deciding who decides.
LEADERSHIPBurnout and Load: Sustainable Pace, Not Heroes
The person who saves every sprint is a single point of failure. On-call load and the signs of quiet overwork.
LEADERSHIPGrowing a Team: Five People and Fifteen Are Not the Same Job
Past seven, communication paths multiply. When to split, Conway's law, and what "two pizzas" really says.
LEADERSHIPManaging Up: Setting Expectations, Not Filing Reports
When do you say "the sprint will slip"? The arithmetic of early bad news, and shielding versus hiding.
Engineering
Concurrency, distributed systems, messaging, scaling and coding with AI — all with real incidents and code examples.
Race Conditions: Why Does Stock Go Negative?
Invisible in staging, catastrophic on sale day. Six fixes, with SQL examples.
ENGINEERINGDistributed Locks: Getting It Right
Six traps in a Redis lock, fencing tokens, and the fact that most cases need no lock at all.
ENGINEERINGWorker Sharding: The Right Way to Split Work
Four workers, one at 100% CPU and three idle. Hot keys, rebalancing and ordering guarantees.
ENGINEERINGHow Pod Scaling Actually Works
Pods went from 4 to 24 and the system got slower. Why is CPU the wrong metric?
ENGINEERINGVibe Coding Rituals
Why does three hours of work turn into two days of debugging? Ten habits that work.
ENGINEERINGLeader Election: Who Does This Job?
Four copies, all running the health check. Leases, split-brain and fencing tokens.
ENGINEERINGHow Many Times Does a Message Arrive?
At-least-once, at-most-once and the exactly-once myth. Idempotency keys and dedup, with code.
ENGINEERINGQueue Pathologies
Poison messages, DLQs, jitter, head-of-line blocking, reordering and backpressure — all five.
ENGINEERINGFailure Modes
Thundering herds, cache stampedes, cascades, circuit breakers, gray failure and failover loss.
ENGINEERINGDistributed Transactions: Why 2PC Blocks and Saga Saves You
One leg filled, the other rejected. Compensating transactions and the escrow pattern.
ENGINEERINGThe Dual Write Problem: Outbox, Inbox and CDC
The order was written but the event never published. Why atomic dual writes are impossible.
ENGINEERINGCQRS and Materialized Views
The portfolio screen takes 8 seconds, the order path needs 3 ms. Separating reads from writes.
ENGINEERINGWhere Did the 200 ms Go?
Six services add up to 40 ms while the customer waits 240 ms. Correlation IDs and traces.
ENGINEERINGMonolith to Microservices: What Five Months Taught Us
The distributed monolith, double shipments, a cancelled order at the door, and the two services we merged back — with numbers.
ENGINEERINGLogs and Metrics in Microservices: One Screen, Not Six Log Files
Prometheus, Loki and Grafana on one screen. The four golden signals, structured logs, a 2.4-million-series cardinality accident, and why the CPU alert was useless.
ENGINEERINGDon’t Say “I Have an SMS Code, I’m Safe”: Step-Up Authentication with Passkeys for Withdrawals
The JWT was valid and $4,800 went to a new IBAN. A challenge bound to amount and IBAN, a free margin re-check, and the back door on the “add passkey” screen.
ENGINEERINGSOLID: A Tool, Not a Goal — When to Use It, When to Skip It
Two interfaces, two classes and a factory for a one-line welcome message. The five principles with code; the signals where they help, the cases where they only add files; YAGNI and the rule of three.
Who this is for
If sprints keep spilling over and nobody looks at the retro actions; if you keep postponing the hard conversations in your team; or if your system runs perfectly in staging and falls over on the morning of a campaign — you are in the right place.
The three sections are really the same team’s three different problems: process, people and systems. And they are usually connected — the answer to why a sprint spilled over is sometimes in a queue design, and sometimes in a sentence nobody said out loud.
Every post ends with a checklist; if you are in a hurry, read only those and share them with your team.