Coding is an very important part of programmer's daily work. But beyond coding, programmers need to do other work as well, they need to fix bugs reported by users, they need to write documents for their codes. Also, they often need to answer questions from customers, bosses and colleagues. What do they often say when they are facing different sort of questions? Today we share some.
- It's done. I just need to clean up a few things.
- This is hacky, but I'll fix it soon.
- This can never happen:
- It's just a one-line change so it shouldn't affect anything else.
- This task will be easy.
- Yeah, I tested it.
- I'm almost done.
- If there's a bug, it can't possibly be in my code.
- Yeah, it is a known bug.
- I'll add the Unit Test case in the next release.
- I'll comment and document my code later.
- It's not a bug, it's a feature.
- I will finish it by evening it's almost done.
- Works on my machine -- That's not a lie, haha
- The code was working few minutes ago
- It's 90% done
- I'm deeply investigating requirements. Will start development soon.
- It's just a temporary solution, it won't be used in production. --Actually this is usually from production manager not programmers.
- I'll add it to the TODO list
- That's easy, it'll just take a couple of days.
- The bug isn't in my code; you are using it incorrectly.
- I'll just cut-and-paste this code for now, but I'll make a super-class when I have a moment.
- I'll add unit tests in the next code change.
- This is a hardware issue. Nothing to do with software
Have you wondered why programmers like saying these? Are they not willing to admit their errors? Are they lazy to fix their bugs? The reason why they are saying these may be that they are usually too confident, they cannot allow others to doubt their codes. Do you have any other opinion?
