Throw in:
Battlezone
Stargate (defender upgrade)
Joust
Doom
T-Mek
Descent
Mortal Combat
Virtua Fighter
Space Lords
Police 911
Crazy Tax
Nethack
Rtype
BattleTech (mech pods version)

Always go in with a well considered plan, and be there when it happens.

Even if your planning is awesome, you'll look unprofessional not being in a position to fix a problem when it is most likely to occur.

If something does happen, and your not there.. There will be crankiness.

Any episode with Q was horrible. (John Delancy was great)
Holodeck centered episodes -- lame (Barkley's stuff was passable)
Any episode focused on Troi, Data,or Wesley, were really bad.
Worf or Geordi episodes were more palatable.

My favorites:
Arsenal of Freedom
Inner light
Thine Own Self
Peak Performance
Who Watches the Watchers
The Defector
The Hunted
Best of Both Worlds

If he's reaching the interview phase, it isn't the job market.
Almost nobody want's to interview more candidates than necessary. It's a huge hassle and the cost is pretty damn high.

Baseline is that in an interview I try to determine a few things:
1. Ability to perform work. Can you be in consistently, and perform work that is of an adequate quality/quantity to be worthwhile?
2. Ability to work with the team. Are you going to damage morale, will you communicate in a manner that doesn't cause excess problems.
3. Ability to not upset the exterior of the team, will a person dress/speak appropriately around customers/ bosses/ HR
For likability go for candor.
Some people feel uncomfortable with that, if so go with a mistake that could have been averted by another party -but- take full ownership of it. Leave enough of the story in there so that the interviewee can see that it was another party mistake, but not enough that it appears blatant. An instance might be making a bad commit to the code base, realizing it too late, then finding out that the svn repository died horribly AFTER everyone had pulled out YOUR broken update. Then have some canned speech about how you stopped mixing the debug and production directories from that point on.

Lot's of developers are intolerably arrogant, and there are a bunch of queue's that the interviewers are looking for, show that you can hide these signs. Talk yourself up in a way that doesn't show arrogance.

I've come in to work with some gross frickin coffee makers.
Or finding the grinder lid is no where to be found on Monday morning.
If you stash your next grinder you're considered some kind of pretentious schmuck. So you get some cheap POS grinder, just to find that the coffee filter is gone the next Monday. You grab some paper filters, and find that someone tried to brew stronger coffee by using five filters at once, making an ever loving mess of the coffee pot/kitchen area

I like that it is really inconvenient for someone else to make the brewing part go nasty/break on a K cup system.
Knowing that I just grab a pod and have fresh brewed caffeine in 20 seconds is comforting.

I've been interviewing people for higher end stuff, and keep getting applicants that don't know jack.
Are lost at the Ax=b
Haven't heard of Valgrind

All this from interviewees that are conditioned to believe that all these requirements are just HR flak to be ignored.
Those HR people have stolen hours from me indirectly.

A Passionate Programmer != Good Developer
A good developer cares about their craft, a passionate programmer cares about their code.

Honestly, most managers would be clueless as how to deal with a passionate programmer.

The meetings, conference calls, the coding conventions, the documentation, making hard choices that hurt the deeper beauty of the finished product. This is poison to the passionate programmer. Other people doing substandard things to her code. This isn't ok to do to someones passions. It would be like letting a person bring a pet to work, and the staff kicks it at a whim.

They want people who pretend to be passionate. But really their looking for employees that want a paycheck, and a good portfolio when they leave.

Fedora 21 (Black Jack)
I'm calling it that, and I dont care if Fedora leaves it nameless.

Bitcoins can be broken down to very small values. Allowing a bitcoin to inflate to a crazy value without impacting spend-ability..

The dark matter theory has always felt a bit contrived to me. But I don't have the background to make an cogent argument against it, nor have standing for my words to carry weight.

The All clears an ambiguity. This means the poster means that all the print drivers have most of their stuff in userspace. Rather than most of the print drivers are in userspace.
I don't follow printer drivers closely enough to know if the poster was right. I try and follow the nuance language, it is abused often.

Why own the car at all? Might as well be a service, no point in having "your" car a couple miles away doing nothing.
You could summon a car, based on all sorts of criteria. Mostly I see the big use case as a taxi-van, where a ride sharing system could be in place. Sure a person could request a private car, but I suspect that many people would be happy to share a ride with people who have been matched by computer as good ride matches.

They're sysadmins, They'll have the same sentiments as other federal employees that get downsized. Some will transfer to other USG jobs, Then they'll check the big iron jobs, fortune 500 companies, top500.org (some quasi governmental work there). University, State and Municipal IT positions.

The last stack of resume's I looked at was deeply disappointing.

They have a freakload of data. Where the access to the data must be secured, compartmentalized, logged, verified, and audited. Keys must be managed in a much more robust way. Ensuring that no data can leak between running jobs on a cluster.

There are going to be a freakish amounts of sysadmins/systemprogrammers/cybersecurity type all trying to meet the needed requirements. Then hoping that none of them get so rushed that they cut a corner, and leave a vulnerability open.

I'm sure that doing 10x work will result in full diligence.