Eating habits of developers

This one started out as an internal joke, but it has become quite generic :)

  • Java developers always go to eat together, in pairs, hand in hand, well organized (synchronized)
  • PHP devs go at random times, some of them run, some walk, some take the elevator. (loose coding style)
  • DB devs choose someone, who will then go to kitchen and fetch the food for everyone (also known as proxy)
  • Delphi devs get the plate, put it in the center of kitchen, then get a fork and then walk between the food containers and plate, until plate is filled (drag ‘n drop)
  • C devs kill their own animals and eat them raw (low-level)
  • C++ devs prepare their food from prefabricated components in microwave oven (not that low-level)
  • Frontend (HTML) devs decorate their food with cucumbers, tomatoes and generally everything else in the fridge and then play around with it until the food is cold
  • Python devs always take the stairs (mandatory stepping) (from Jaagup Irve)
  • Perl devs bring their own food to the work and eat it alone in the corner, while everybody else is giving them weird glances (You call THAT food? eewwwww) (syntax)
Thursday, June 12th, 2008 at 12:37
  • Jun 12th, 2008 at 13:50 | #1
    Procedure MyOpinion;
    begin
     while delphiProgramming do
       begin
        editCode;
        eat;
       end
    end;
  • Jun 12th, 2008 at 16:27 | #2

    How do PHP, Java, Python and other developers go to eat?

  • MediaBlitz
    Jun 12th, 2008 at 19:13 | #3

    Javascript devs phone a pizza. (AJAX)

  • damog
    Jun 13th, 2008 at 04:55 | #4

    Perl?

  • Jun 13th, 2008 at 09:22 | #5

    Added Perl too :)

  • Jun 14th, 2008 at 22:59 | #6

    My take:

    Python developers always insist having some space between the ingredients (indentation).

    Python developers treat every ingredient in a special way. (everything is an object)

    Java developers will first argue who’s responsibility it is to get the food, then they decide collectively the manager should fetch it (IoC).

    Java developers prefer the most complex way of eating their stuff. Just putting() the Fork with the Food in the Mouth is too simple. At least they need a ForkInterface extending the TableToolsInterface complemented by the CanBeUsedToEat annotation, implemented by extending the BasicTableTools class, overriding the put() interface. Just so it’s easy to do something else with that fork.

  • Jun 15th, 2008 at 08:28 | #7

    Daan, that is even better :)

Comments are closed.