Coding terminology explained

Mailed around the company this morning:

What we say: Horrible hack
What we mean: Horrible hack that I didn’t write.

What we say: Temporary workaround
What we mean: Horrible hack that I wrote.

What we say: It’s broken
What we mean: There are bugs in your code.

What we say: It has a few issues
What we mean: There are bugs in my code.

What we say: Obscure
What we mean: Someone else’s code doesn’t have comments.

What we say: Self-documenting
What we mean: My code doesn’t have comments.

What we say: That’s why it’s an awesome language
What we mean: It’s my favourite language and it’s really easy to do something in it.

What we say: You’re thinking in the wrong mindset
What we mean: It’s my favourite language and it’s really hard to do something in it.

What we say: I can read this Perl script
What we mean: I wrote this Perl script.

What we say: I can’t read this Perl script
What we mean: I didn’t write this Perl script.

What we say: Bad structure
What we mean: Someone else’s code is badly organised.

What we say: Complex structure
What we mean: My code is badly organised.

What we say: Bug
What we mean: The absence of a feature I like.

What we say: Out of scope
What we mean: The absence of a feature I don’t like.

What we say: Clean solution
What we mean: It works and I understand it.

What we say: We need to rewrite it
What we mean: It works but I don’t understand it.

What we say: emacs is beter than vi
What we mean: It’s too peaceful here, let’s start a flame war.

What we say: vi is beter than emacs
What we mean: It’s too peaceful here, let’s start a flame war.

What we say: IMHO
What we mean: You are wrong.

What we say: Legacy code
What we mean: It works, but no-one knows how.

What we say: ^C^C^X^X^X^XquitqQ!qdammit[esc]qwertyuiopasdfghjkl;:xwhat
What we mean: I don’t know how to quit vi.

Tagged , . Bookmark the permalink.

Comments are closed.