Recently @ThePracticalDev asked people on Twitter for typical things programmers say:
There were a lot of great answers. Here are my favorites:
- It works on my machine.
- It’s not a bug, it’s a feature.
- How hard can it be?
- How did that even work in the first place?
- I don’t see anything in the logs.
- I’m guessing it’s an issue on their side.
- Probably some kind of permissions issue.
- That’s weird.
- That’s a known issue.
- We don’t support that.
- No, I don’t know how long it’s going to take.
- Actually, it has always been like that.
- Have you tried it with Chrome or Firefox?
- It should work now.
- But that’s not how you told me it should work.
- Well there’s your problem right there.
- Working as intended.
- I mean, everything’s *possible*…
- That will never happen.
- Shouldn’t take too long.
- Cheap, fast, high quality. Pick any two.
- It’s 90% done.
- This is just a temporary fix
- You’re doing it wrong
- That’s a code smell.
- I thought we fixed this!
- Yes, but does it scale?
Words and Expressions
There were also individual words or expressions:
- Rabbit hole
- Turtles all the way down
- Yak shaving
- // TODO
There were also several sites mentioned:
- Excuses for bad programmers (with the full list here)
- Programming excuses
- Bug fix bingo
- Top 20 Replies by Programmers
- The Jargon File
PS. If you don’t follow @ThePracticalDev you should – lots of good tweets!