Commentary

Last CIO Standing: Joke Contest Results

How many CIOs does it take to screw in a light bulb? That age-old philosophical question's not as easy to answer as you might think. Here are several responses to our CIO Joke contest.

How many CIOs does it take to screw in a light bulb? That age-old philosophical question's not as easy to answer as you might think. Here are several responses to our CIO Joke contest.>> Two. One to hold it up and the other to nail it in place.

>> [[A multiple entry]] A. It only takes one, but he has to have one programmer to write the bulb removal program, another to write the insertion program, and a third person from the security office to make sure no one else is trying to change the light bulb at the same time as his team.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

B. One, but he needs a consultant to tell him which end to insert into the socket.

C. Only one, but we'll have to go out and buy the light bulb adapter card first, which is extra.

D. We could just have marketing promote the dead bulb as a feature.

E. We've formed a quality circle to study the problem of why light bulbs burn out and to determine the best thing we as managers can do to enable light bulbs to work smarter, not harder.

>> Just one. Just once. He put in a fluorescent, low-energy dim bulb and we can't find the office anymore.

>> Initial studies indicate that only one is needed. However, we have not been able to complete the analysis. The customer requirements are scheduled for delivery in two weeks and then we need to get bids from three independent outsourcing firms before the work can begin.

>> [[Another multiple entry]] A. None. CIOs aren't afraid of the dark.

B. One. But a team of analysts and consultants must insure that all Sarbanes-Oxley requirements have been met and that the implementation is PCI compliant.

>> It's a trick question. CIOs don't change bulbs. It's against the collective bargaining agreement. A grievance would be filed before the end of the day.

On the off chance that you might be foolhardy enough to seek a replacement bulb from the CIO, you'd be asked to send an e-mail to the Help Desk instead of bothering the CIO with a legitimate question, get an automated reply saying that your e-mail has been received, then two weeks later, when you bump into one of the techies, you'll ask about your light bulb and they'll tell you that "management" has decided that not everyone needs a light bulb at their desks and, instead, each department will now be sharing one overhead fluorescent. In the event that the fluorescent tube needs changing, a work order will need to be filled out and submitted to the Operations department and then there will be a two-week lag time once the job is entered into the work-order calendar. By then, you've wandered away babbling about how you can see just fine by the glow of your LCD monitor...

>> [[Another multiple entry]] A. Define light bulb.

B. Three. One standing on a chair while gripping the bulb and two others to raise the chair and rotate it clockwise.

>> Only after a discovery call and sizing are completed can the answer to this question be determined.

>> We'll never know for sure. It's not in the SLA ...

Not funny enough for you? I'd like to see you come up with something funnier.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links