I often can't remember jokes. But google is my friend. I particularly like 3, 4, 8, 10, 11:

Quote

How many software engineers does it take to change a light bulb?

1. None. "We'll document it in the manual." 2. None. It's a hardware problem. 3. One, but if he changes it, the whole building will probably fall down. 4. Two. One always leaves in the middle of the project. 5. Four. One to design the change, one to implement it, one to document it, and one to maintain it afterwards. 6. Four, plus one senior analyst to manage the project, one technical writer to correct the spelling and grammar of the one who documented it, one light bulb librarian, a sales-force of at least five to drum up enough users who want to turn the light on, 274 users to burn out the new bulb, at which point we go to tender for another light bulb change,... 7. Five. Two to write the specification program, one to screw it in, and two to explain why the project was late. 8. Wait! Maybe the bulb isn't broken. Let's try it again. 9. It's hard to say. Each time we separate the bulb into its modules to do unit testing, it stops working. 10. The change is 90% complete. 11. We looked at the light fixture and decided there's no point trying to maintain it. We're going to rewrite it from scratch. Could you wait two months? 12. Only one, but she's not available. She's the only programmer we have who can get the <insert name here> software ready to ship to customers, and that's higher priority, you know. 13. Of course, as everyone knows, just five years ago all it took was a bunch of kids in a garage in Palo Alto to change a light bulb.

I get home from work, and my four year old daughter is sitting in the living room on the floor, under a blanket (over her head, covering her whole body), talking on the cordless phone to my mother-in-law.

I often can't remember jokes. But google is my friend. I particularly like 3, 4, 8, 10, 11:

Quote

How many software engineers does it take to change a light bulb?

1. None. "We'll document it in the manual." 2. None. It's a hardware problem. 3. One, but if he changes it, the whole building will probably fall down. 4. Two. One always leaves in the middle of the project. 5. Four. One to design the change, one to implement it, one to document it, and one to maintain it afterwards. 6. Four, plus one senior analyst to manage the project, one technical writer to correct the spelling and grammar of the one who documented it, one light bulb librarian, a sales-force of at least five to drum up enough users who want to turn the light on, 274 users to burn out the new bulb, at which point we go to tender for another light bulb change,... 7. Five. Two to write the specification program, one to screw it in, and two to explain why the project was late. 8. Wait! Maybe the bulb isn't broken. Let's try it again. 9. It's hard to say. Each time we separate the bulb into its modules to do unit testing, it stops working. 10. The change is 90% complete. 11. We looked at the light fixture and decided there's no point trying to maintain it. We're going to rewrite it from scratch. Could you wait two months? 12. Only one, but she's not available. She's the only programmer we have who can get the <insert name here> software ready to ship to customers, and that's higher priority, you know. 13. Of course, as everyone knows, just five years ago all it took was a bunch of kids in a garage in Palo Alto to change a light bulb.