Technical debt, meant as the damage created to a codebase by hastily implementing a feature (and wrecking the codebase’s design in the process), seems to be a foreign concept to some managers/customers. Maybe they know and they just don’t want to listen, I’m not sure. Anyway, I thought of a little story that I might use the next time I’ll have to explain the pricing of some new feature:

A farmer has three chickens. Each chicken makes one egg per day.

The farmer is in business with a local grocer. The grocer buys two eggs per day from the farmer, so he can sell them at his shop.

All is fine with the world until the grocer shows up at the farmer’s place:



Grocer: Hey there. I'd like to have some chicken meat today.

Farmer: Meat? That wasn't in the agreement.

Grocer: I know. But I really need meat. It's for a Business-to-Stomach Enterprise Poultry-as-a-Service Platform I'm planning.

Farmer: What?

Grocer: Important stuff. Can you give me some?

Farmer: Well, that's not so easy - I'd have to hatch eggs and wait for the chicks to grow... I think it'll take a month or so.

Grocer: A month? That's way too much... I was thinking more on the likes of right now.

Farmer: Nature has its times, you'll have to wait a little bit.

Grocer: Hm, why don't you just kill one of the chickens? That way, I'll have my meat and you can still produce two eggs per day. You don't need more, right?

Farmer: Well, I don't think it's a good idea. That would put me in a tight spot in the case something happens to one of the other chickens.

Grocer: Come on, nothing's going to happen... and I really, really need that meat! Can you do that?

Farmer: Okay, I guess I can...



And so, the farmer picks his cleaver up and sends one of the birds to the Creator. The grocer gets his meat and returns to his shop.

One week later, the grocer pays the farmer another visit:



Grocer: Hey there!

Farmer: Hey, what's up?

Grocer: Listen - the meat was great. Actually, it was so great and it sold so well that now we absolutely need at least another chicken. By tomorrow.

Farmer: That's not gonna happen. If I give you another chicken then I'll not be able to deliver the two daily eggs that were in the pacts.

Grocer: Oh please come on! Customers want meat, and I've already promised it for tomorrow...

Farmer: No, I can't do that. I'll not be able to honor the contract if I do, do you understand? Eggs will not be guaranteed if I do that.

Grocer: But I really, really, really need the meat! By tomorrow! Otherwise customers will get mad, the earth will shatter and the world as we know it will end! Give me one of the chickens, now!

Farmer: Well, if you want it that bad, take it! Again, eggs are not guaranteed from now on, understood?

Grocer: Yea sure, got it. But you're a smart guy, I guess you'll figure out how to make it work anyway. Bye!



And the grocer leaves for his shop again.

The day after:



Grocer: Hello. What's wrong with the eggs?

Farmer: What do you mean?

Grocer: The eggs. Actually, the egg. There's just one. What happened?

Farmer: What happened? I had three chickens. You took two. Now there's just one. One chicken, one egg. I though I was being clear about that.

Grocer: But that wasn't in the pacts! The contract states it right here - you owe me two eggs per day! Now what will I say to my customers?

Farmer: Well, I was very clear about it. Nothing I can do about that.

Grocer: Okay, okay, sheesh, forget it. Talking about something else... it would be nice to have some meat. Can I have some?



So, don’t be a farmer – refuse to irreparably damage your codebase for the needs of now and, if you’re forced to do so, don’t take responsibility for the wreckage – and don’t be a grocer – don’t ask for the impossible and assume the responsibility for your decisions.

P.S.: no chickens were harmed during the writing of this blog post.