How to incur technical debt

I guess you’re worried that when your project has no bugs, or when maintenance becomes too easy, someone is going to start wondering what they’re paying you for. What you need is technical debt. Here my top 10 ways to sneak some into your codebase. As well as plenty of future bugs, this will ensure that any maintenance or expansion tasks take as long as possible.

1. Create lots of overloaded versions of the same function. Only use one.
2. Copy and paste code. For bonus points, change the pasted versions slightly.
3. Leave chunks of commented out code (“Green Code”) lying around.
4. Don’t use existing core logic. Reimplement it within the user interface using your own strange methodology. Make sure it behaves subtly differently. No need to check that, it will.
5. Check several unrelated changes in at once. Only mention one in the check-in comment.
6. Never use 5 lines of code where 50 will do.
7. Never use 50 lines of code where several classes that almost resemble a GOF pattern you misunderstood will do.
8. Invent your own naming conventions.
9. Never fix a bug – hide it. For example, deal with null reference problems by simply sticking an if-not-null around the offending code. This saves you having to look for the real source of the problem, and also ensures the bug will come round again in a more subtle and interesting manner.
10. Leaving out documentation is too obvious. Much better to document it, but make sure the code doesn’t do what the documentation claims.