How long? What amount of time passes between you saving the file you just changed and you seeing the results of that change? If that answer is over 10 seconds you might want to wonder if you can make it shorter. If that answer is over 100 seconds, please consider making a radical change in your approach. Thinking is the bottleneck, not typing, we’ve been over this a bunch. But waiting you can bypass — all waiting you can bypass […]
The expense of an integration test can be extremely high. Consider the contentment app. This app makes drawings 1) that distribute across time, as if they were being drawn live in front of you, 2) that are generated stochastically, 3) with a "pixel-inaccessible" framework. Now, it’s important to understand that none of these problems are insurmountable. Before you tell me how you’d surmount them, let me tell you how I could. 1) screw time. Rig it so it draws as
TDD: Resist Integration Tests See Full Post
An old blog of mine, We’re In This For The Money, recently got some attention, delighting me, of course. A full h/t to Jim Speaker @jspeaker for that! He quoted me thus: Too busy to #TDD? Too busy to pair? Too busy to #refactor? Too busy to micro-test? I call bullshit. My buddy Erik Meade calls it Stupid Busy, and I think that nails it pretty well. All you’re really saying is that you’re too busy to go faster. ~@GeePawHill
My TDD Isn’t Judging Your Responsibility See Full Post
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
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
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
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
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
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
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
