Change Quote by Scott McNeely
““Q: How many Java programmers does it take to change a lightbulb? A: One, to generate a “ChangeLightBulb” event to the socket. Q: How many C++ programmers does it take to change a lightbulb? A: You’re still thinking procedurally. A well-designed lightbulb object would inherit a change method from a generic lightbulb class. Q: How many Windows programmers does it take to change a lightbulb? A: Three. One to write WinGetLightBulbHandle, one to write WinQueryStatusLightBulb, and one to write WinGetLight-SwitchHandle. Q: How many database programmers does it take to change a lightbulb? A: Three. One to write the lightbulb removal program, one to write the lightbulb insertion program, and one to act as a lightbulb administrator to make sure nobody else tries to change the light-bulb at the same time. Q: How many software engineers does it take to change a lightbulb? A: None. That’s a hardware problem. Q: How many Microsoft engineers does it take to change a lightbulb? A: None. They will redefine darkness as an industry standard.””
About This Quote
A series of jokes highlight how different programming cultures approach problem‑solving, emphasizing over‑engineering, procedural thinking, and the absurdity of redefining problems.
In simple terms: Programming jokes about over‑engineering and culture.
Key Takeaway
Avoid unnecessary complexity.
Themes
programming culture
humor
software design
abstraction
process
Mood
lighthearted
satirical
Type
joke
industry critique
When to use this quote
- code reviews
- team meetings
- software architecture
Key Concepts
over‑engineering
procedural vs. object‑oriented
industry satire
Questions to Reflect On
- What practices reduce over‑engineering in teams?
- How can humor improve tech communication?
A Different Perspective
Humor may reinforce stereotypes about developers.
