Pro-Tip

TDD Pro-Tip: They Work For You, Not You For Them

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 i’m digging at what I do over and over, and sharing it.) One difference I see over and over between noobs and olbs is the …

TDD Pro-Tip: They Work For You, Not You For Them See Full Post

TDD Pro-Tip: Suspect Demeter Chains

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 demeter chain out of whatever the object is that contains that assignment. A is our direct collaborator. We might have been passed her, or given …

TDD Pro-Tip: Suspect Demeter Chains See Full Post

TDD Pro-Tip: Time Needs Technique

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 of an additional argument, you get perfect testability. The price of resistance? Your now-based object will have to be thought about every time you place …

TDD Pro-Tip: Time Needs Technique See Full Post