GeePaw

Use Supplier Or Supplied Or Both?

TDD, Geekery, Technique / / 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

Coaching, Geekery / / 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

TDD, Geekery, Modern-Synthesis, Technique / / 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

TDD, Geekery, Modern-Synthesis, Technique / / 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

Coaching? Like People | Video

Coaching / / 4 minutes of reading

Hey, there, it’s GeePaw! And you are watching the first ever GeePaw video aimed specifically at coaches. I hope you like it. Do you know what the first absolute prerequisite for being a successful software development coach is? You have to like people. You have to like people. You have to like their style. You have to like their resistance. You have to like when they do the thing you want them to do. You have to like when they

Coaching? Like People | Video See Full Post

Coaches: Whence Confidence?

Coaching, Geekery / / 4 minutes of reading

Coaches, we all know that confidence is key, yes? It’s not the only key, but it’s key, especially in the beginning. People look to you for ideas, then. And they’re lookinig to you for a number of reasons, but one of those reasons is because they think you’ll have some. And early on, there’s very little reason for them to think that. They don’t know you, they are guessing. And that perceived confidence in them is matched by an internal

Coaches: Whence Confidence? See Full Post

No One Way: GeePaw On Method

Geekery, Modern-Synthesis / / 4 minutes of reading

When I was geek-young, not quite forty years ago, I worked in a tiny two-person shop, and we were entirely without "method". We just wrote code. At that time, there were plenty of analysts of geekery, and they were certainly writing about how to geek, but 1) their ideas were seen as more of a bazaar than a cathedral, and 2) most of the trade did exactly what we did at good ol’ MIS. (Chris Martz, or Jan, if you’re

No One Way: GeePaw On Method See Full Post

The First Metric: How Are You Feeling?

Geekery, Modern-Synthesis / / 4 minutes of reading

Of all the routine requests I get from clients, the one I find most difficult to deal with is this: "Help us choose a metric so we can tell if things are going well." the problem is that "numbers as health indicators" is so deeply embedded in our worldviews, so deeply correct on paper, and so deeply counter-productive in every case i’ve seen in practice. Think about your own health for a minute. Is it a 9 or a 3?

The First Metric: How Are You Feeling? See Full Post

TDD & The Geek-Young: Is Tdd Right For Noobs?

Coaching, TDD, Geekery / / 4 minutes of reading

Possible causal point for a failure to value TDD: geeks thinking the main source of bugs in professional software is not handling the main case successfully. In any feature in any app, there are one or more primary cases. A given story is likely to be concerned with one of these at a time. When you’re geek-young, the great challenge is just to close out the primary case. Hell, you barely learned the syntax, you’re just learning the library-set. Just

TDD & The Geek-Young: Is Tdd Right For Noobs? See Full Post

Scroll to Top