You have a system that reviews the reviewers, allowing for weighted values of reviews. Not that slashdot users would have heard of mod points or metamoderating.

What I want are the full instructions on how to get software X to function on a known good configuration.
I'm talking ALL the instructions, as in I have a box with the minimum Fedora v 26 install, what are all the keystrokes that I will need to install this software. No assuming that I will have X set up some way on my machine, or that I've installed the right version of Mesa3D, or that vim is installed.

I don't want to find out that I'm hunting down some bug because yum install kerberos installed MIT kerberos instead of Hemidall kerberos.
I want this because almost everyone skip steps they consider obvious. The puzzle is so much easier to figure out when you can look at the picture on the lid.

Baah... The kicker is that The Doctor is like your uncle when your three years old. Sure the monster in the shoe-box is scary, but your uncle know's it's only a sock. boom now he's running from the monster too, all good fun. Figuring out how to stop a sock monster is fun, but not a real threat.
The Doctor has technology that is so insane that it dwarfs any problem he's in. Heck, the sonic screwdriver is probably much bigger on the inside, utilizing power that might rival a small star.
The plot holes are amazingly huge.. 2 companions get trapped in NYC past. because it's tough to get a Tardis to them, they never consider taking a plane to London or LA. Or having the long lived doctor just park early and just meet them in NYC in a few years. Now either the Doctor has horrible writers, or they are ok with the Doctor stranding his friends in a workable past.
The deus ex machina is the goal of most of the episodes.

Ok,
1. Ban corporations from politics. The government is for the people. No money, no lobbying.
2. Require "news" to be a purely independent enterprise (syndicated) with barriers that prevent monetary coercion.
3. Change the law drafting practices. So a complex law cannot simply be drafted by a corporation that create calculated loopholes. The people "hacking" the legal system really need to be stymied.
Any of the above would be a huge boon the country.

only the 8250, the 16450 and 16550 were slackers.

And I'd bet if asked if he REALLY understood Linux, he'd be saying nope.
There is something to be said for being comfortable with not knowing everything.

I snagged one of the keyboards a couple years back. Nothing else compares for typing. I have an old das keyboard, which is very good, and feels so much better for fps gaming. The F key lost some clickyness. but it's still an awesome choice to type on. The big kicker is that it has the windows key (nifty for moving windows on multiscreens) and a usb interface. It has a freaky long cord which can be handy. The loud clicks can be a bit rough on coworkers.

Good coding style can catch those mistakes.
A normal function
if (state=1) {do stuff;}
has some issues, but with a consistent style
if (1 = state) {do stuff;}
GCC will throw a compile time error that it obvious, rather than strange behavior that has to be hunted down.
Style is far more than tabs and spaces. When and how variables are initialized, do you populate them with error flags, do you have some byzantine check for correctness states. Or do you have a big pile of intermediate variables to determine the state. Do you have a assume true with a disprove, or assume false with a prove X as true.
style matters

I think 298 degrees would be more reasonable. No reason to risk superfluidity.

The big problem that I see with the H1B is that the holders of the H1B are at far too much mercy of their sponsor. Putting aside any talk of fairness for the foreign nationals, this is still a bad thing for domestic labor. By having a class of people beholden to their sponsor, it reduces the negotiating power of remainder. If the employer upgrades the job duties, the H1B holders can't balk at the request, without fear of reprisal.

Years ago I had a junior technician working on my crew with an H1B, he was a bright Iraqi fellow with a Ph.D in Physics. Middle management had him doing programming work for $8.50 an hour with plenty of OT.. With cuts looming in the near future he was safe but that meant that someone else would be taking the cut. So I had to get him a promotion within the company to ensure the safety of my crew.
Since that experience I have really hated the way H1B works. Though I don't have animosity t'ward the H1B holders.

I don't believe that Americans came from the British, because there are still British people. Clearly Americans came from a Creator, and we owe him the decency to stop claiming that many Americans are simply the descendants of Europeans.

right there with you man.

So then how would you feel if upper management asked you to press a button for "bathroom", where the information would be available to the operators.. You know for solidarity.

I guess I see the bathroom button as a huge sign of disrespect. If a friend asked me how long I was on the can I'd tell them none of your damn business. Now when you realize that someone is taking the efficiency of your defecation into the equation it's horrible. Every frikkin aspect of their time is watched like a hawk, just logg it as personal time and call it good. By treating people like property your going to have horrible retention problems.

Reliability and power.. more memory is more chances for a node to have a failure, ram gets hot, and so it will need to be cooled. And my bet is that it is ECC-DDR3, as el-cheapo isn't remotely worth the price in these applications.

This is a total load of manure.
Installing software is a pain in the rear end, and I've been doing it for a bunch of years. The googling for an error message is rarely as simple as it seems, as you run into all sorts of outdated information, or information for something other than the distro your using.
Then you run into a segfault, or the code just exits for "no reason" and then dig through the documentation/ code/ message boards to find that variable X in the config file must be an exact multiple of variable Y


The other side of this thing is horrible too... I was required to write code (GUI / 3D / interactive/ with Web Access) that would install and work under linux (redhat /debian/ suse) and windows. And it had to be easy enough for an average user to install
Found a nasty behavior in my code this week where my fog only worked on full 3d objects but not lines, when used on a nvidia/intel hybrid graphics laptop. As I was trying to show a friend how robust/awesome my code was. A little change to his laptop settings, and he was properly impressed, though his battery promptly drained.
Anyway expecting a user figure out that their in "hybrid" mode is a pretty onerous expectation of a programmer..
Really as a programmer I think that of your releasing code out to be used by the average joe, it should just work.

For any program a programmer should provide a step by step guide of getting working software from a minimal install of the target OS's/Distro's
Anything less is just lazy. Have a couple of test files in the tarball/RPM/DEB that will prove that the program can run properly.
If every chunk of software had this piece to it, the world would be a better place.

The traces in the chips are 2.5 atoms thick, the distance between traces is 22nm for the most modern production technique, there is some room for squeezing it down a bit more, but there aren't many more significant drops in size that can be made.
GPGPU has a long way to go to be flexible enough for general purpose work.
Besides the real push needs to be the push for less power per op, at 1GF/watt, exaflops are a problem.