Earlier quoted context omitted.
If JavaScript was specified to the same degree as the Hubble telescope then the OP wouldn't have had a problem. Blaming gdubs's education is a bit problematic.
The ECMAScript spec is actually quite thorough and freely available to read online. In addition, it has a very large suite of tests to check for compliance. I don't think there's any other language with as many independent production-quality implementations. In what way do you think it could be better specified?
Hubble is back
21–30 of 128 posts
Re: Hubble is back
#22Earlier quoted context omitted.
It's also fun to compare programming to surgery, where they work for hours straight with no backup on a production system that is actively trying to die.
It has always amazed how hard it must be to debug an issue in a human being, you need to check A, B, and C, but if you check C your human will be scared since it could indicate your human has cancer, if you check B it will be expensive since it involves a lot of studies, you can also check with A giving some medicament but it also is expensive and maybe other people needed more. So you end up testing all three, but n…
Re: Hubble is back
#23“Last week the operations team commanded Hubble to perform numerous maneuvers, or turns, and switched the gyro between different operational modes, which successfully cleared what was believed to be blockage between components inside the gyro” And here I am on Earth, barely capable of debugging JavaScript code.
Re: Hubble is back
#24I will never cease to be impressed by the sheer skill and quality of design at NASA, that allows them to keep missions like Hubble or Opportunity operating far beyond their planned lifetimes.
Re: Hubble is back
#25Amazing. It's like they performed the Epley Maneuver on a satellite. https://en.wikipedia.org/wiki/Epley_maneuver
Re: Hubble is back
#26“Last week the operations team commanded Hubble to perform numerous maneuvers, or turns, and switched the gyro between different operational modes, which successfully cleared what was believed to be blockage between components inside the gyro” And here I am on Earth, barely capable of debugging JavaScript code.
> And here I am on Earth, barely capable of debugging JavaScript code. If as much education was required of software engineers as it is from people who work on the Hubble telescope then you wouldn't have any troubles debugging JavaScript.
Obviously such measures would be very much impractical outside of NASA.
Re: Hubble is back
#27- some NASA scientists, probably
Re: Hubble is back
#28“Last week the operations team commanded Hubble to perform numerous maneuvers, or turns, and switched the gyro between different operational modes, which successfully cleared what was believed to be blockage between components inside the gyro” And here I am on Earth, barely capable of debugging JavaScript code.
It's also fun to compare programming to surgery, where they work for hours straight with no backup on a production system that is actively trying to die.
But also surgeons make misstakes. Lots of them. Or don't find the perfect solution in time, needed to save someones live.
Re: Hubble is back
#29Reading about the specs and the planned degradation of the gyros is a very interesting exercise in planned reduction of a service. They know the gyros will eventually give out and they have contingency plans around what kinds of science they can continue to do even when they're down to 1 gyro. Very impressive. I'm always discouraged hearing people say NASA is wasting money and science and that's just not true IMHO.