If u think the semaphore mechanism in your library works, then test to the level of setting the semaphore. If u think it doesn’t work, then u need another library or o/s. Testing across threads is for people who are testing semaphores. If u think that your JSON transport works — from your UI’s perspective […]
What TDD Tests Prove Read More »
When you think back to first generation Hamurabi, and then play Oxygen Not Included, or Civilization or any of the other current world-builder games, you see the power of steady accretion of improvement. Do you know that all of this has happened well within my lifetime? I played Hamurabi in 1979, killing time in the
Take A Minute To Just Marvel: GeePaw on Coaching Read More »
A Simple Optimization Problem Hey, it’s GeePaw! Got a little optimization issue for you. Let’s look at some code. It’s easy stuff, so I’ve just used pseudocode here. Take a look. The program starts by entering a loop that runs 50 times. Inside that loop, it calls the Read method. It then enters another nested
Optimizing A Program (And Programming) | Video Read More »
Okay, fine. Geeks and geekery it is. What do these words point at for me, and why do I use them? You know, asking this, there’s no way in hell i’m gonna answer without wanting to share my decidedly minority views about language. You just know that. Please be advised that I know that these
Geeks And Geekery: Why I Use These Words Read More »
Continuing last night’s wobbly muse on graceful and awkward collaborators… In the light of day, I think I see four possible responses to the situation when your new code depends on an awkward collaborator or collaboration: Ignore it (possibly just for now). Write your test anyway and suffer the expense. This is a legitimate judgment,
Awkward and Graceful 2 (A Recovery) Read More »
Software Programs can be understood as (potentially huge) orchestras playing in concert. Depending on your level of abstraction, you might imagine systems, subsystems, layers, packages, objects, or even functions as the individual players. (Aside: Folks often make major distinctions in these abstractions, but to my touch, they feel all the same thing, just with ever
Awkward and Graceful Collaborators Read More »
Five Underplayed Premises Of Test-Driven Development (Transcript) Hey, it’s GeePaw! I’m here to tell you today about five underplayed premises of Test-Driven Development. These premises form the kind of fundament under which almost all TDD proceeds. And when I say that I’m a TDDer, I almost always mean I am operating inside the little ring
Five Underplayed Premises Of TDD | Video Read More »
Time, finally, for the steering premise, from the five underplayed TDD premises. The steering premise says "tests & testability help steer design & development". What we’re saying here is that tests are first-class citizens in the mob of factors that shape our system, with a voice that counts, all the way through development. Think of
Underplayed: The Steering Premise In Depth Read More »
Today, let’s talk a little about the chaining premise, from five underplayed tdd premises. The chaining premise says "test a chain by testing its links". Like the other premises, it’s easy to make it pithy, but it has vast ramifications about when we’re doing TDD. When we talked about the money premise, I gave a
Underplayed: The Chain Premise In Depth Read More »
The judgment premise is one of five underplayed tdd premises. The judgment premise is simple to word and vast in its extent. It says, "tdd relies absolutely on individual humans using their human judgment." you might ask yourself, "what doesn’t rely on human judgment?" but there are lots and lots of activities that are entirely
Underplayed: The Judgment Premise In Depth Read More »
