TDD Pro-Tip: Prevent complex test data from spiraling out of control by going to builder & custom comparator early on. The push-to-small, coupled with SOLID, coupled with things like third normal form, all lead us to a place of wanting to compose domain objects into potentially very rich dependency graphs. A card in a address-tracking […]
TDD Pro-Tip: Start Builders & Partial Comparators Early Read More »
I’ve mentioned "acculturation" a couple of times lately. Let’s dig in a little deeper on that. In our trade, we make much of "education", training and learning and skills inventories and such-like. I say we make much of it, well. That’s an overstatement, of course. Companies talk about it a great deal. But i’m often
Acculturation: A Little Deeper Read More »
TDD Pro-Tip: "No, smaller." In TDD, almost without exception, we want everything: a test, a method, a class, a step, a file, really, almost everything, to be as small as it can be and still add value to what we’re doing. This is the most common gaping hole in the practice of the noob, and
TDD Pro-Tip: ‘No, Smaller. Read More »
So, I’m out there slinging advice about how to change the world of being a professional programmer. Maybe y’all need to hear some things about that, that might not have occurred to you. I am just some schmoe. I am having a successful life in the world of geekery. There are a host of causes
Slinging Advice and Where I Come From With It Read More »
TDD Pro-Tip: TDD and refactoring are permanently intertwined activities, neither of which can be grasped all at once, so start learning how to write tests at the same time you’re learning how to change code w/o adding bugs to it. Some activities are what I think of as "life games". The better you get at
TDD Pro-Tip: TDD & Refactoring Are Intertwined Life-Game Read More »
TDD Pro-Tip: remember who works for who, and shape your tools to your hand, not your hand to your tools. (Btw, these tips are in no particular order. If you want to know the truth, i’m musing them as I do them. People always know more than they can say, and i’m no exception, but
TDD Pro-Tip: They Work For You, Not You For Them Read More »
TDD pro-tip: demeter chains are anti-microtestable. What is a demeter chain? It’s code where we talk to a collaborator’s collaborator. U can look up the origins of the name in your copious free time, but in regular code, it looks like this: x = a.b.c.d.e.f; each one of those dots is a link in a
TDD Pro-Tip: Suspect Demeter Chains Read More »
TDD pro-tip: any "time" u refer to a clock, be on the lookout. It’s a time — I just can’t help myself — to seriously microtest your way through. If you have to talk about "now", consider whether you want to be able to pass a clock rather than call the system. For the price
TDD Pro-Tip: Time Needs Technique Read More »
We spoke of two questions in the recent re-visiting of the money premise. How/why does TDD make changing layered branching logic faster? What’s the capital outlay to change to it? I’ll stall a little further on 2, but let’s do 1. Some provisos before we get started, and they’re pretty important. Proviso #1 We are
How TDD Makes Change Faster Read More »
Time, this morning, to return to the underplayed TDD premise called the money premise. In one phrase: "We’re in this for the money." What does that mean? In the software business, like every other business in a long period of very high demand, we make more money when we ship more value faster. Please be
We’re In TDD For The Money Read More »
