Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Define BAD (Score 1) 507

Bad is such a subjective word. Bad as opposed to what? Bad how?

To me Bad code is:
Uncommented, obfuscated, sphagetti, poor structure, follows no name or calling conventions, uses unnecessary tricks to accomplish it's goals, uses soon-to-be deprecated functions, code that just plain doesn't work and above all non-portable.

Comment Re:Mark this one for the history books, folks. (Score 1) 183

Why not take some of that steam generated by the primary and run a failsafe turbine that doesn't generate electricity. It should just run pumps to keep the secondary cooling system running in the event of electrical failure. This way, even if the system has been flooded, cooling continues AND the hotter the primary gets, the faster the turbine will turn and the more cooling should be effected.

Comment Re:Hmmm ... (Score 1) 755

Well, here we have two opposing views of programming. On the one hand, we've got the Systems style programmer who can bootstrap a machine using binary digit displays and toggle switches. On the other hand we've got a Scriptor who uses canned programming.

There are pros and cons to both approaches:
The Systems programmer will take longer to do the job, assuredly. But, when he's done, the result will be tight fast efficient code that will get the job done in a fraction of the time a script could.
The Scriptor can probably hack together something that will get the job done but will not scale well. You'll need a supercomputer/Beowulf cluster to handle the load.

My opinion is: Use the scripting languages to prototype and make the final product a compilation like C/C++/PASCAL etc...

C++ is Object Oriented and it is also compiled. Best of both worlds.

Slashdot Top Deals

The rule on staying alive as a forecaster is to give 'em a number or give 'em a date, but never give 'em both at once. -- Jane Bryant Quinn

Working...