Nuke the server from orbit. It's the only way to be sure.

Oh come on, you think your little niche is the whole world? A modern day "real programmer" wouldn't waste any time on a shitty 8bit processor.

I did my time in the 8bit 6502 days. I loved them. Those days are gone.

If you're not coding 64bit then you are stuck in the past. Tell yourself anything you want, but if you are still coding on a 8bit processor then you are horribly obsolete.

Now there's something I haven't heard about in a LONG time...

I'm no fan of Java-based curricula, for the same reason I'd be no fan of Fortran-based curricula. Computing isn't about one language. Each language and system shows you one hyperplane of a vast multidimensional space. The best programmers know lots of languages, and choose wisely among them — or even create new ones when appropriate.

In the production world, there are times where some C++ or Java code is appropriate ... and there are times when what you want is a couple of lines of shellscript and some pipes ... and there are times when the most sensible algorithm for something can't be neatly expressed in a language like C++ or Java, and really requires something like Common Lisp or Haskell. If you need to exploit multiple processors without getting bogged down in locking bullshit and race conditions, you're much better off using Go than Java.

(Just last night, at a meetup, I was talking with two bright young physicists who reported that their universities don't do a good enough job of teaching Fortran, which is the language they actually need to do their job. Scientific computing still relies heavily on Fortran, Matlab, and other languages well removed from what's trendy in the CS department — no matter if that CS department is in the Java, Haskell, or Python camp. But if you want to learn to write good Fortran, you basically need a mentor in the physics department with time to teach you.)

And there are times when the right thing to do is to create a new language, whether a domain-specific language or a new approach on general-purpose computing. There's a good reason Rob Pike came up with Sawzall, a logs-analysis DSL that compiles to arbitrarily parallel mapreduces; and then Go, a C-like systems language with a rocket engine of concurrency built in.

(And there's a good reason a lot of people adopting Go have been coming not from the C++/Java camps that the Go developers expected, but from Python and Ruby: because Go gives you the raw speed of a concurrent and native-compiled language, plus libraries designed by actual engineers, without a lot of the verbose bullshit of C++ or Java. Would I recommend Go as a first language? I'm not so sure about that ....)

What would an optimal computing curriculum look like? I have no freakin' clue. It would have to cover particular basics — variable binding, iteration, recursion, sequencing, data structures, libraries and APIs, concurrency — no matter what the language. But it can't leave its students thinking that one language is Intuitive and the other ones are Just Gratuitously Weird ... and that's too much of what I see from young programmers in industry today.

When I was with a startup during the dot com era, it seemed to me that the worker bees were on speed, while the executives were on coke. I could see what the worker bees were doing, but nothing else could explain the decisions made at the upper levels. The incentives were pretty obvious--long hours without sleep, and demand to be 'on' regardless of circumstance, and the arrogance that comes with mastering a small domain and thinking you've mastered everything (see Dunning-Kruger.)

Personally, when I was tired, what I craved was sleep. But that was frowned upon. You can see why so many did drugs.

Arrogance, though, is a major consideration. Notice the parent comment: If you take drugs and get addicted... but no one plans to get addicted. Oh, take drugs by all means, just don't get addicted. They take drugs to cope, and as they are masters of the universe, they could not possibly get addicted. Besides, it's just to meet this deadline... and the next... and the next...

The entire culture is a massive fuck-up. Tired people make mistakes, and mistakes cost money. In the 1850's they discovered that 40 hours a week was the sweet spot for productivity, and every generation since has had to discover the same thing the hard way. I cannot count the number of projects I have seen crash and burn because of this bullshit.

But fuck it. We're John Galt. We can do anything. Just another bump to get me through...

How's that working out?

It sounds like this transformer had its center tap grounded and was the path to ground on one side of a ground loop as the geomagnetic field moved under pressure from a CME, inducing a common-mode current in the long-distance power line. A gas pipeline in an area of poor ground conductivity in Russia was also destroyed, it is said, resulting in 500 deaths.

One can protect against this phenomenon by use of common-mode breakers and perhaps even overheat breakers. The system will not stay up but nor will it be destroyed. This is a high-current rather than high-voltage phenomenon and thus the various methods used to dissipate lightning currents might not be effective.

In March 1989 much of Quebec lost power for the same thing.

They lost power because the common-mode breakers tripped, not because their system was actually damaged.