March 2018

Use Supplier Or Supplied Or Both?

Technique, Geekery, TDD / / 4 minutes of reading

A coding pattern; replace supplied data with a supplier or a supplier with the supplied data. It is very common to create code with an interface like this: do( Data supplied ) We then use the data somehow to perform our functionality, whatever a do(…) method does. On the other hand, sometimes we create code with an interface like this: do( DataSource supplier ) And its body is basically the same as our starting chunk, but with a prolog that […]

Use Supplier Or Supplied Or Both? See Full Post

Methods Don’t Create Health

Geekery, Coaching / / 5 minutes of reading

Maybe the real first wrong was the slide into "method" in the first place. Have you ever known yourself to behave in a way that is generally perceived as neutral or even positive, but in a way that is actually doing you or others harm? Depressive Solitaire My work makes me think a lot. And I quite often do that thinking on a low boil in the background, as i’m doing something else, most often for me playing a game.

Methods Don’t Create Health See Full Post

How I Get Them To Do What I Want

Coaching, Geekery / / 5 minutes of reading

A little more on coaching theory today… Folks ask me a lot of questions whose fundamental focus could be expressed as "how do you get them to do what you want them to do?" so. Here goes. I hereby reveal my entire competitive advantage as a professional coach, by telling you my special secret for how I get them to do what I want them to do. I don’t. I don’t get them to do what I want them to

How I Get Them To Do What I Want See Full Post

How To Test Depends On What To Test: Money, Chaining, And Steering

Technique, Modern-Synthesis, Geekery, TDD / / 6 minutes of reading

To have a serious conversation about how to test, we have to start by considering what to test. As a microtesting TDD’er, what I want to test is our logic. Enter the Money Premise The money premise of TDD reminds us we’re in this for the money, that is, the primary purpose of TDD is to enable us to ship more value faster. Deciding what is "value" is not a TDD task. The larger agility certainly asks us to make

How To Test Depends On What To Test: Money, Chaining, And Steering See Full Post

Avoid Implementation Inheritance: GeePaw Goes All Geek-y

Technique, Modern-Synthesis, Geekery, TDD / / 5 minutes of reading

So, day off before travel before onsite, playing ONI, having fun, but I want to muse about a highly geeky matter anyway… Do you ever override in a sub-class a method that’s already implemented in a super-class? I want to recommend to you a policy of avoiding that like the plague, whenever you can. I will go further: I avoid, maybe not as much as the plague, but surely as much as the measles, even deriving any sub-class off of

Avoid Implementation Inheritance: GeePaw Goes All Geek-y See Full Post

Scroll to Top