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 […]
Use Supplier Or Supplied Or Both? Read More »
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
Methods Don’t Create Health Read More »
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 Read More »
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
How To Test Depends On What To Test: Money, Chaining, And Steering Read More »
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
Avoid Implementation Inheritance: GeePaw Goes All Geek-y Read More »
