See subject.

I'm just going to leave this here: https://en.wikipedia.org/wiki/...

If you want native speeds, use the OS. This is doing nothing more than complicating development - now rather than just OS differences you have every possible permutation of OS and browser to deal with when bug fixing.

1) Failure is an integral part of success. Don't give up when you fail, learn from it and grow.

2) Understand people, tell her to read "How to win friends and influence people" and commit it to heart. No matter what she does she will always need to understand people. Learning how to deal with humans and their silliness will give her more success than any geeky persuit alone. It'll also make her life much happier.

I wish I'd learnt both of these things when I was 20.

I'm sure you are right, but don't fight the name man, don't fight the meme! :)

Why would anyone want to listen to this lunatic?!

pass is the equivalent of a nop, it has nothing to do with scoping. Have you ever read or written any python?

Was it really worth breaking your screen over though? :)

...particularly physicists who think they can code.

Deal with people....

Games development on linux? Do you work for Valve?

If the US got hit by a mega tsunami it would have a lot more to worry about that a few nuclear plants getting flooded and melting down. The death toll from a mega-tsunami would probably push into the millions. Displaced people... many many more.

Anyway, even if they do melt down, the more modern reactor designs have systems for capturing and spreading the corium to reduce the possibility of uncontrolled runaway (ie it would just ruin the reactor and would not necessarily pollute the area).

Make sure you launch them into something interesting. I would recommend a raytracer - the basics are incredibly simple, but they can be expanded to great levels of complexity. There is direct visual feedback, so rather than just printing out a load of numbers the users can field like they have achieved something more substantial. Numerical optimization and data structures can be introducted gradually and immediate results can be seen. Raytracers provide a great environment for introducing object oriented programming, they are also trivial to parallelise. On top of all this raytracing is extremely useful and the knowledge gained writing a raytracer, other than the computing aspect, is extremely valuable in engineering and physics (eg the maths + physics behind them).

If you don't want to use a human standing next to the blind singer then it could be solved with some nice cheap modern technology.

If you could practically do it, attach a MEMS accelerometer (or gyro) to the baton and track the velocity of the tip (or equivalent reference point). Either wired or wirelessly transmit that velocity data to small processing box that drives a haptic device to alert the singer. Unfortunately I'm not entirely familiar with the visual clues of conducting, I've had a look at the patterns of motion on wikipedia and it seems the beat occurs at the point of zero vertical velocity following a downward stroke. If this is the case it should be relatively easy to process the velocity/acceleration information. An algorithm that has an understanding of the expected stroke would be better than a simply velocity test - it would potentially be more reliable as it will have a degree of inference, but minimizing latency may make that problematic.

In terms of haptic feedback, a sharp tap to the leg or hand would probably be better than a vibration as it has a more defined temporal position. Of course with a tap the processing algorithm has to be reliable...... alternatively a vibration could simply be engineered so that the magnitude of the vibration corresponds to the vertical position of the baton. This would mean more processing of the information by the singer, but is trivial to build electronically.

An Arduino would be perfect for the processing/driver.

He said mitigated, not prevented. I've (unintentionally) measured the oscillating light output of an incandescent while I was developing an optical trigger circuit for my last job, the intensity dropped by ~20% for this particular bulb (20W desk lamp) during the AC zero crossing. The flickering was 100Hz (funnily enough) - higher than most peoples' periphery will notice.