July 2021

Three Software Engineering Coaches Get Coached By GeePaw Hill (FourScouts TV)

How much are you able to learn on your own? For some people, reading books, articles, and going to certain training courses are all they need to keep steadily growing their skillset. For teams however, things are a bit more challenging. Retrospectives are indeed a great help, but these are still from the team’s own perspective. Sending a team to training could help as well, but how do you know what training to pick? Sometimes external help, in the form […]

Three Software Engineering Coaches Get Coached By GeePaw Hill (FourScouts TV) See Full Post

On (Not) Using Mocking Frameworks

I’m long past on record that I think the use of auto-mockers outside of legacy rescue situations is bad policy. First, it’s easy to write "psuedo-tests" using an automocker. Psuedo-tests are tests that appear to prove things about your code that they don’t actually prove. Now, note, I’m not saying auto-mockers force one to write psuedo-tests. They don’t. But they do make it awfully easy. How? The combination of "don’t care" arguments in mocked method specs with hardwired returns makes

On (Not) Using Mocking Frameworks See Full Post

Three Short Coaching Pro-Tips

A respondent asked that I combine these three short Pro-Tip muses into one post, so here goes: Coaching Pro-Tip #1: Everything good about agility is rooted in relationship, so everything good about coaching is, too. As coaches, we usually start from negative trust, and our central priority has to be reversing that position. In the early days of most coaching engagements, one sees lots of issues, of various size and shape. The temptation to start issuing criticism and directives is

Three Short Coaching Pro-Tips See Full Post

Scroll to Top