Category Change

Refactor Your Tests

TDD Pro-Tip: I spend considerable effort making it possible not only to implement a test I want, but to make that test easy to read, to write, to run, and to debug. I’ve talked a lot about five premises of…
Read More

Try Different, Not Harder

Change Pro-Tip: I give the same advice to myself as a coach that I do to my teams: "Try Different, Not Harder". A while back we covered Alice’s vision of how to change things. In countering it, I offered the…
Read More

Seek Judgements Not Numbers

Change Pro-Tip: I try to prioritize getting human judgments — opinions, reactions, feelings — because the quest for numbers holds too many easy traps. When I go to the doctor, she asks me how things are going. Here’s an answer…
Read More

Finding the Pivot Mount

Refactoring Pro-Tip: When I choose a side-by-side approach, I start by finding (or making) the "pivot mount". the place where the final switchover can take place safely. (So, I re-read that last muse, the one driving this, and I blanched.…
Read More

We Haven’t Seen It All

I was on the road half to two-thirds time for for about 25 years, nearly always visiting or working with software teams. I’ve worked with teams as small as 2 and as large as 500. I’ve worked in the US,…
Read More

Change the Problem

I’ll tell ya a story. Once upon a time there was a team that had it pretty good. They were internal-facing in a VBCA, supporting a variety of analysts of different types, with about 3 dozen small projects clustered around…
Read More

About Interruptions

I saw the five-minute meeting with developer thing again. Not offering it here cuz I don’t much want to give it the publicity. The gist: when you interrupt a developer the time-loss is far greater than the duration of the…
Read More