Five Whys: the number is wrong and the answer usually blames someone
How to run a root cause analysis that ends in a fix ticket instead of a symptom, a philosophy, or a person to be more careful.
10 posts
How to run a root cause analysis that ends in a fix ticket instead of a symptom, a philosophy, or a person to be more careful.
How keyword-driven suites in Robot Framework are built, how they rot, and the maintenance rules that keep them running past month three.
What belongs in a coding standard, what belongs in a config file, and how to enforce the difference with formatters, hooks and CI gates.
How to tell deliberate debt from accidental mess, measure what it costs you, and make the case for paying it down in numbers a manager will accept.
A working mental model of Git — snapshots, pointers, three trees — then the daily commands and how to escape the five situations that scare people.
Red-green-refactor with a worked Python example, what test-first actually buys you, and the places where it earns its keep least.
A practice-by-practice look at Extreme Programming: what became the industry default, what stayed niche, and why the split is mostly about tooling.
The roles, events and artifacts Scrum actually defines, how each one degrades on a real team, and the kinds of work it fits badly.
The phases every software project runs through, why waterfall, iterative and agile only differ in ordering, and how to choose one deliberately.
What the four values and twelve principles actually say, which ones matter in practice, how to spot agile theatre, and when plan-driven is the right call.