|
|
The way I see it…..few assumptions here!
Turn on light switch 1
Wait 1 minute
Turn off light switch 1
Turn on light switch 2
Go to the room with the light bulbs
Light switch 1 controls the light that is warm
Light switch 2 controls the light that is on
Light switch 3 controls the other
Probably a load of rubbish but hey…..
How many kids with Attention Disorder Syndrome does it take to change a Light bulb?
Wannna go play bikes?
Hey, it’s not nice to say things about people with AD…
Sure, I just need to put some air in my tires.
What if they are flurescent bulbs?
Well, you turn switch one on.
Unscrew the mounting cover to switch two.
Attach a circuit tracer to the two bare leads. (use a multimeter to figure out which pair run to the bulb and which run to the main beaker.)
Enter the room. You feel the weight of your Gameboy in your pocket. You know you have Pokemon Silver in there, and you’re just waiting to capture Riachu. But wait, you have to figure out which bulb you need to… save the princess, right? You switch to Mario and happily crush Koopas for hours, all worries of switches and bulbs forgotten.
How about the Management Solution?
Get someone else to flip the switches while you go and watch the light bulbs…
heh I failed this one the first time someone gave it to me, in part due to their description, and in part due to assumptions on my part.
They did not describe a table, or that the bulbs were accessable.. so I’m thinking typical office overhead florescent lights, not accessable..
They had to give me a hint ‘think about the properties of a light bulb’.. at which point I realised I’d made an assumption…
Learned to not make assumptions in interviews, especially where puzzle questions etc are concerned. In fact from what I’ve seen, it is often the norm (at least at one Very Large NorthWest Software Company) to put forth the puzzle WITHOUT enough information to solve it, so as to see if you will:
a) realise you don’t have enough info
b) not make assumptions, or at least verify the assumptions are true.
c) not try to solve the problem without needed info, or based on assumptions.
d) Will ask the right questions to get the info you need.
I tried giving this test verbally to a class full of my peers at ITT Tech and no one got it right, there was some intresting ideas such as rewiring and causing short circuts but I had to remind them that Bill probaly wouldnt like that too much…
Bug Bash is a comic strip written and illustrated by Hans Bjordahl. Bug Bash is a comic strip about technology: managing technology, the business of technology. It's about project management and managing projects through the dull world of Rational Rose, use cases, and requirements. Functional requirements, user requirement, functional specifications, design specifications, call it what you want but it's still the bane of project managers. And when you're done with that, you can think about all the fun that comes with timelines, scheduling, estimates (PERT estimation anyone?) and resourcing until Gantt charts are coming out of your ears. Let's not forget the risk management in the software engineering life cycle. Maintaining the project is just as much fun, managing what was initially set out in requirements and trying to keep feature creep / scope creep in check with change management. If any of these words send nightmares to you, the project manager, then this site probably rings true with you. (Who Links Here?)