Not bad, but I think Barb's was actually pretty good.

I dismissed them as neckbeards and accountants.

I'd argue/debate/discuss it with you, but I find it an issue for the history books. Besides, I think I'm stuck in meetings for five of the next eight hours :(

civilization reaches a point where its porn and virtual reality [preoccupy them]

Until..."I've been hacked! She has 3 green dicks! That I can live with, but not her looking like Kim Jong-Un now."

Next you'll be telling me you can create operating systems in less than 15GB!

If you complain, we'll re-write it in Java and make it 30GB

"illegal moves...may cause...strange things to happen"

Quantum chess, my favorite! Oh wait, that's the prenup fineprint

Do you mean % of software devoted to maintenance? % devoted to "changing data formats"? I know later in the book he claims OOP wraps data formats and therefore allegedly reduces the impact of those on code. But those later arguments are spurious in my opinion when compared to the alternatives. Adapters can be made in any paradigm. And reducing that 18% slice may increase other slices. Either way, those 2 slices are not measures of OOP improvements.

Toldja, 640 bytes otta be enough for anyone. -Gill Bates

I bet other civilizations failed to travel outside their star system because they devoted all their energy to trying to solve the Fermi Paradox.

Yes it is a form of "soft" censorship. So be it. We have to sacrifice some ideals to avoid living in a corporate waste-land. Tradeoffs tradeoffs.

You are free to tune out and make all that money worthless and put the people you want on the ballot.

What "works" for you or me doesn't necessarily scale to the rest of voters.

That's what they get for using double underscores in function names.

Paul Graham partially credits Lisp for making him rich via his store-site start-up, despite having viable competitors. The company that bought him out eventually converted it to a more conventional language stack for day-to-day maintenance.

The next probe will be Zombie 2.

The best "lone wolf" developers probably use something like Lisp and a high amount of math-like abstraction to crank out vast amounts of features in a short time.

However, a good team programmer knows how OTHER typical programmers think and read code, and writes code that is easy for them to navigate, digest, and change. Team programming is more like authoring a good technical manual, not clever gee-whiz tricks.

Indeed. My theory is that many of those mysterious gamma-ray bursts are civilizations earning a Galactic Darwin award.

"Hey look, we can create mini anti-black-holes in our la ~ ^ & [NO CARRIER]