Coding Horror: New Programming Jargon

July 20th, 2012 § 0 comments

There are so many great terms here and I really want to bring some of them into my lexicon. Particularly:

8. Heisenbug:

A computer bug that disappears or alters its characteristics when an attempt is made to study it.

I hate those kind of bugs and it’s going to make me feel better having a name for it.

14. Baklava Code

Code with too many layers.

Baklava is a delicious pastry made with many paper-thin layers of phyllo dough. While thin layers are fine for a pastry, thin software layers don’t add much value, especially when you have many such layers piled on each other. Each layer has to be pushed onto your mental stack as you dive into the code. Furthermore, the layers of phyllo dough are permeable, allowing the honey to soak through. But software abstractions are best when they don’t leak. When you pile layer on top of layer in software, the layers are bound to leak.

.NET anyone?

23. Rubber Ducking

Sometimes, you just have to talk a problem out. I used to go to my boss and talk about something and he’d listen and then I’d just answer my own question and walk out without him saying a thing. I read about someone that put a rubber duck on their monitor so they could talk to it, so rubberducking is talking your way through a problem.

I have done this many, many times. Am I right Jesse?


Follow me on twitter.

Leave a Reply

What's this?

You are currently reading Coding Horror: New Programming Jargon at Thomas Paine Rants.

meta