Tag Archives: Programming

What I learned about programmers by reading 200+ programming jokes

Programmers think differently and are exceptionally logical. Computers are too literal. Programming languages are illogical. The world is illogical. People are irrational.


The Apico blog editor dug into more than 200 programming jokes and noted to her surprise that they covered all of four topics.


Don’t anthropomorphize computers. They hate that!

2.1. SHOES

Q: How do you tell an introverted computer scientist from an extroverted computer scientist?
A: An extroverted computer scientist looks at your shoes when he talks to you.


A guy was crossing a road one day when a frog called out to him and said, “If you kiss me, I’ll turn into a beautiful princess.” He bent over, picked up the frog and put it in his pocket.
The frog spoke up again and said, “If you kiss me and turn me back into a beautiful princess, I will stay with you for a week.” The guy took the frog out of his pocket, smiled at it and returned it to his pocket.
The frog then cried out, “If you kiss me and turn me back into a princess, I’ll stay with you and do anything you want.” Again the guy took the frog out, smiled at it and put it back into his pocket.
Finally the frog asked, “What is the matter? I’ve told you I’m a beautiful princess, that I’ll stay with you for a week and do anything you want. Why won’t you kiss me?” The guy said, “Listen, I’m a programmer. I don’t have time for a girlfriend, but a talking frog is really cool.»”Read at APICO

Rubber Duck Problem Solving: “Ask the Duck” is a very powerful problem solving technique

I explained Rubber Duck Programming to some coworkers and loved Jeff Atwood’s article on the subject


Jeff Atwood of Coding Horror writes:

I love this particular story because it makes it crystal clear how the critical part of rubber duck problem solving is to totally commit to asking a thorough, detailed question of this imaginary person or inanimate object. Yes, even if you end up throwing the question away because you eventually realize that you made some dumb mistake. The effort of walking an imaginary someone through your problem, step by step and in some detail, is what will often lead you to your answer. If you aren’t willing to put the effort into fully explaining the problem and how you’ve attacked it, you can’t reap the benefits of thinking deeply about your own problem before you ask others to.

Read more from the source: blog.codinghorror.com