How many VB programmers does it take to change a light bulb ?

**G.Kumaraguru** · May 27th, 2000, 02:55 PM

Help..

I need an Answer for this.
How many VB programmers does it take to change a light bulb ?

This is the first question Microsoft Visual Basic Certification exam ...

May 27th, 2000, 07:43 PM

Are you serious?

**Fox** · May 27th, 2000, 08:06 PM

0 - it's a hardware problem

**Shabble** · May 27th, 2000, 09:17 PM

471; one to write

Code:

GetLightBulbHandle() as hnd

, one to write

Code:

QueryStatusLightBulb() as Boolean

, one to write

Code:

GetLightSwitchHandle() as hnd

...

**Fox** · May 27th, 2000, 09:33 PM

2 - One holds the light bulb and the second turns the chair around

**Juan Carlos Rey** · May 27th, 2000, 09:46 PM

None, a pianist can do it with his left hand.

(Sorry, wrong forum...)

If it were here in Argentina, I would say 3: 1- one to actually change the bulb, 2- other to make the berbecue (no big work goes out without one) 3- a government inspector to certify that the work is well done.

**Fox** · May 27th, 2000, 11:05 PM

I'd say 100... One for changing the bulb and 99 to click the error messages

May 27th, 2000, 11:41 PM

I would say 4

1 to write this

Code:

Type LOCUDT
X As Long
Y As Long
End Type

1 to write this

Code:

Declare Function GetBulbHandle Lib "Bulb32" (ByVal LocationX As LOCUDT, ByVal LocationY As LocUDT ByVal Watt As Integer) As Integer

1 to write this

Code:

Declare Function SetBulbPos Lib "Bulb32" (ByVal NewLocX As LOCUDT, ByVal NewLocY as LOCUDT, ByVal BulbHandle As Long)

and one to write this

Code:

Sub SetPos()
Dim lngRet As Long
Dim lngBulbHandle As Long
lngBulbHandle = GetBulbHandle(500, 60, 100)
lngRet = SetBulbPos(500, 60, lngBulbHandle)
End Sub

Private Sub Command1_Click()
Call SetPos
End Sub

there, it takes 4 VB programmers to change a lightbulb

**kedaman** · May 28th, 2000, 02:29 AM

I'd say all programmers in universe.

If we remove one programmer we have our universe collapse in mass decrease, so we need all programmers to be online

May 28th, 2000, 02:35 AM

138072701

There's a lot more programmers than that!

**kedaman** · May 28th, 2000, 02:48 AM

How do you know that meg?
Maybe we have
1
or
31409750237456923469282973459345978
but theres probably
138072701
because, that's what my app told me

May 28th, 2000, 03:56 AM

What's this App do? Count all the people in the world?

**Shabble** · May 28th, 2000, 06:23 AM

Originally posted by Megatron
What's this App do? Count all the people in the world?

Hmm - not sure that you need an app to do that <g>

FWIW, according to http://metalab.unc.edu/lunarbin/worldpop there's just over 6 thousand million (6e9) on the planet at the moment.

Projections only go up to the end of 2037, where (according to this) there'll be 10 thousand million people (1e10).

May 28th, 2000, 06:34 AM

6 thousand million, is the same as 6 billion

**Shabble** · May 28th, 2000, 06:45 AM

Originally posted by denniswrenn
6 thousand million, is the same as 6 billion

Ohhh - that largely depends on which side of the pond you're on I think <g>

from http://www.mcn.net/~jimloy/billion.html

Code:

Number of zeros   U.S. & scientific community   Other countries 
3                 thousand                      thousand 
6                 million                       million 
9                 billion                       1000 million (1 milliard) 
12                trillion                      billion 
[snip]

[Edited by Shabble on 05-29-2000 at 01:03 AM]

**kedaman** · May 29th, 2000, 02:44 AM

number of zeroes
[snip]
600 centilion
[snip]
999999999999999999999999999999 kedamaniljon
infinity

Ok my app does calculate this from a formula:
Amount of people/amount of kedamans + amount of megatrons ^amounts of shabbles mod amounts of denniswrenns

May 29th, 2000, 04:35 AM

Code:

Amount of people/amount of kedamans + amount of megatrons ^amounts of shabbles mod amounts of denniswrenns

= 6000000000
 ------------
  1 + 1^1
      ---
       1


= 6000000000
  ----------
    1 + 1

= 6000000000
  ----------
      2

= 3000000000

There, using your formula, there are 3,000,000,000 programmers.

**Yonatan** · May 29th, 2000, 06:11 AM

One writes code which changes the bulb, and all the others try to figure out his code.

**kedaman** · May 29th, 2000, 06:35 AM

Ok, the formula didn't work except that the answer is correct. We have exactly 168072701 programmers, 138072701 was a typo

Code:

?168072700/1+1^1/1
 168072701

so there must be 168072700 people, ok who is the 168072701th guy? The values are in hex, so you probably know what causes that

**Shabble** · May 29th, 2000, 10:49 PM

Originally posted by kedaman

Code:

?168072700/1+1^1/1
 168072701

so there must be 168072700 people, ok who is the 168072701th guy? The values are in hex, so you probably know what causes that [/B]

Operator precidence I assume - try

Code:

?168072700/(1+(1^1/1))

Nowt to do with hex I'm afraid.

**kedaman** · May 30th, 2000, 12:26 AM

Why not?

May 30th, 2000, 02:42 AM

168072700 is not the number of people in the world. It's 6 billion. your formula said that it suppose to be the number of people in the world.

**kedaman** · May 30th, 2000, 03:04 AM

Meg, it is hex:6040266496 in dec

May 30th, 2000, 03:32 AM

Why i type that number in my Windows Calculator, the numbers change...when i switch from dec to hex than back to dec. The hex value stays the same but the dec doesn't.

**Shabble** · May 30th, 2000, 04:41 PM

Originally posted by Megatron
Why i type that number in my Windows Calculator, the numbers change...when i switch from dec to hex than back to dec. The hex value stays the same but the dec doesn't.

Windows calulator has a small problem - it's limited to the numbers it can display in hex.

The maximum number it can display (when converting between bases) is:
4,294,967,295 decimal or
FF,FF,FF,FF hex

Typing in 4,294,967,296 then converting to hex converts it (internally I assume) to 1,00,00,00,00 hex which gets truncated - at the top end. All that's left is 0 which is (one hopes) the same in both decimal and hex.

Basically any numbers over 4,294,967,295 are treated mod 4,294,967,295 until they're under 4,294,967,295 for the purposed of conversion from and to hex.

The above applies equally to octal and binary conversions also.

There - that's 10 minutes wasted <g> Perhaps I should do some work now - I'm sure there's something more constructive that I can do other than pick M$ Calc to bits :)

**kedaman** · May 30th, 2000, 05:00 PM

Hehe, got you now, shall i post the function?

**Michael** · May 30th, 2000, 05:23 PM

Only 1 to actually change it - but at least 10 managers / supervisors to give an opinion on the best way to "achieve the objective"

**gfk** · Jun 1st, 2000, 05:47 PM

It only takes 1 programmer if you download this file:

http://www.vb-world.con/home/electri...changebulb.ocx

Jun 1st, 2000, 09:19 PM

How many VB programmers does it take to change a light bulb ?

How many times did the programmer press f1?

**|2eM!x** · Apr 5th, 2005, 09:52 PM

yay1

**BodwadUK** · Apr 6th, 2005, 03:03 AM

0 they tell the client its a 'Feature' that means they need the new version of the software for their home pc

**timeshifter** · Apr 6th, 2005, 04:24 PM

One to search for the current hardware's driver.

One to code a driver for the new hardware.

One to create an interface between the current hardware and the new driver.

One to update the BIOS on the current hardware. (LightBulb^TM ME was obselete, so they needed a LightBulb^TM XP OS to support the new software.)

One to design a program to automatically eject the current hardware.

One to catch the old hardware as it falls and inspect it for bugs.

One to design a program to install the new hardware.

One to actually interface the current hardware with the new driver.

Five to test the new hardware's compatability with the old hardware.

Three to go tell the manager that they got the problem solved.

Hmm.. sounds like you need 16 to me...

**techgnome** · Apr 6th, 2005, 04:46 PM

Originally Posted by timeshifter

One to search for the current hardware's driver.

One to code a driver for the new hardware.

One to create an interface between the current hardware and the new driver.

One to update the BIOS on the current hardware. (LightBulb^TM ME was obselete, so they needed a LightBulb^TM XP OS to support the new software.)

One to design a program to automatically eject the current hardware.

One to catch the old hardware as it falls and inspect it for bugs.

One to design a program to install the new hardware.

One to actually interface the current hardware with the new driver.

Five to test the new hardware's compatability with the old hardware.

Three to go tell the manager that they got the problem solved.

Hmm.. sounds like you need 16 to me...

Then add 2 more to convince the boss they need to move to LightBulb.NET so they can use LB#.

Tg

**|2eM!x** · Apr 6th, 2005, 10:31 PM

oh just to let you know, my goal was to bring the oldest topic i could find back

**timeshifter** · Jun 6th, 2005, 10:31 AM

Having done significant research, I found that my prior answer was slightly flawed and have made the appropriate adjustments, leaving the final answer to be:

One to search for the current hardware's driver.

One to code a driver for the new hardware.

One to create an interface between the current hardware and the new driver.

One to update the BIOS on the current hardware. (LightBulb^TM ME was obselete, so they needed a LightBulb^TM XP OS to support the new software.)

One to design a program to automatically eject the current hardware.

One to catch the old hardware as it falls and inspect it for bugs.

One to design a program to install the new hardware.

One to actually interface the current hardware with the new driver.

Five to test the new hardware's compatability with the old hardware.

Three to go tell the manager that they got the problem solved.

Two to try and convince the manager that LightBulb^TM.NET is much more efficient and less costly.

One to write a brand new driver for LightBulb^TM.NET and interface it with LightBulbHolder^TM XP.

Three to debug the new system.

One to tell the manager that the project was scrapped due to an anomoly in LightBulb^TM.NET.

One to hire an electrician to take care of the problem professionally.

Thus, the correct answer is 24.

**timeshifter** · Oct 15th, 2006, 02:30 PM

Hold on... after late breaking techniques in the art of light-bulb changing, I've determined that there are actually 3 needed for the last step...

**monoptic** · Oct 15th, 2006, 03:30 PM

Windows users are mentally incapable of attending to any kind of light-fitting malfunction.

**timeshifter** · Oct 15th, 2006, 03:32 PM

I'm sorry... I don't have much choice... and XP Pro treats me good...

**monoptic** · Oct 15th, 2006, 03:36 PM

"There's always a choice Luke."

Thread: How many VB programmers does it take to change a light bulb ?

Thread Tools

Display

Probably 138072701

Zillions....

All the programmers in the world.

M$ Calc

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Re: How many VB programmers does it take to change a light bulb ?

Posting Permissions