Introducing Bad Code Offsets

Very clever! In my grand naivete I assumed that my $.50 would go toward actually cleaning up bad code, but instead, it decreases the relative impact of my bad code by producing more bad code, which will help distract from mine.

Also, I think that the idea is not that stupid. Bad code have many (business also) consequences and I can imagine a savvy company that punishes teams for poorly written code with similar mechanism.

For instance, let's say that team has $100k bonus budget for a year. Every poorly written SLOC means $1, or $10, less in a budget because the company has to spend this money on QA or customer service.

Of course, what's really complicated is how to measure poorly written code (cyclomatic complexity, length of methods etc. basic metrics?), and how to adjust it to the deadlines.

I'd say both of these parodies show why carbon offsetting doesn't really work.

---

When you cheat on your partner you add to the heartbreak, pain and jealousy in the atmosphere.

Cheatneutral offsets your cheating by funding someone else to be faithful and NOT cheat. This neutralises the pain and unhappy emotion and leaves you with a clear conscience.

Can I offset all my cheating? Well, first you should look at ways of reducing your cheating. Once you've done this you can use Cheatneutral to offset the remaining, unavoidable cheating.