Scrum and DevOps both have a retrospective phase. Many teams use it to solve frictions. That’s generally a bad practice. The Problem With Waiting A retrospective keeps the friction alive until the meeting. If a […]
Tag: Software Engineering
DevOps Is Mistaken for a Software Development Model, Unfortunately
Another team in my company runs DevOps. They own an important piece of infrastructure that my system depends on. Every important release takes my system down. Not sometimes. Every important release. The pipeline passes, the […]
I Distilled DeepSeek into a Swarm of JS Functions, Manually
I needed a JavaScript function that extracts label-name associations from text. Instead of writing one function, I distilled a swarm. A note on why this was manual. The obvious approach is to call an API […]
How Do Tasks Flow in Albatross, Compared to Scrum and Kanban
Most comparisons of Scrum, Kanban, and Albatross are about philosophy. This one is about cells. Five people. Sixty days. The same work, done three ways. One cell is one person, one day. The cells show […]
Kanban Can Run Bad
Kanban can run bad. Not straying away from being a Kanban, but running straight into a strangling mess. That’s the part people miss. Kanban doesn’t just let bad work through. It produces it. A card […]
Why Scrum Has Sprints
Scrum does not support parallel development of features. Not because it forbids it. Anyone can split a team across two features. It’s that Scrum gives the team no way to know whether the split is […]
Why Agile vs. Waterfall Is a False Choice
Every sprint is a mini-waterfall. Every Kanban board is a view of Waterfall’s middle phases. The debate assumes teams chose either Agile or Waterfall. Most teams are running both — and the methods don’t describe […]
AI Won’t Replace Programmers, Until …
Or: the body is here, but the mind is somewhere else There’s a genre of article that says AI is about to replace programmers. The subtext is always: the age of the human coder is […]
Why Tech Debt Never Gets Repaid — It’s Not Visibility, It’s Incentives
Every article on technical debt prescribes the same treatment: make it visible. Track it. Put it in the same system as features. Dedicate sprint time to it. Map where friction is worst. The assumption running […]