How many hardware engineers does it take to change a lightbulb?
None: "We'll fix it in software."
But I looked at this, and based of my background in hardware, thought that that wasn't nearly enough people to address a problem of this magnitude. So, based of past encounters, I tried to think of how many people it would actually take to change a lightbulb in an engineering organization:
1 hardware engineer to document the issue and suggest a workaround in software,
1 hardware manager to raise the issue in a status meeting,
1 software manager to note the impact to software,
2 directors to argue about whose department should take the schedule hit,
1 VP to say he doesn't care whose problem it is, but it needs to ship next week,
3 software engineers to code it up at the last minute,
5 QA engineers to confirm that it's horribly broken,
and 1 marketing person to pitch the resulting mess as a "random-phase variable intensity light".