How much red could a red-hat hat…

lol… if they had a job that was ONLY writing unit tests, I would take it!

Kind of the reverse… more lamenting the loss of QA and SRE roles in favor of mechanical (AI) code reviewers and non-technical persons rubber-stamping an increasingly deep pipeline that change requests must traverse.

With that typo, it sounds like a personal insult. :)

Open the pod bay doors…

I recall a carnival-type installation, were a whole house was built at an angle, and at the end of it they had a water spigot they turned on, and the water flowed “uphill” (to the human eye).

The trick is to have a second EFI partition. One for windows to destroy, and one for linux to enjoy.

Well how about that… all this time I thought they were the same character. IIRC, child-me thought it was Wile E’s day job so that he could afford all those ACME products.

https://looneytunes.fandom.com/wiki/Wile_E._Coyote

Organ (powerful deep tones, not the high whistles)

Getting flashbacks of me trying to explain to a mac user why using sudo “to make it work” is why he had a growing problem of needing to use sudo… (more and more files owned by root in his home folder).

The boob that launched a thousand forum threads.

I hope it’s not “worse than useless” (which would mean “misleading”), as my goal was simply to find more identifiers for discussion or research beyond those provided: norway, thorium, 1959…

According to GPT-4.1:

In 1959, Norway achieved a notable milestone by starting up its first nuclear reactor, the JEEP I (Joint Establishment Experimental Pile), located at Kjeller. This reactor was primarily used for research purposes, including early experiments with alternative nuclear fuels such as thorium. While JEEP I itself was not a thorium reactor per se, it laid the groundwork for subsequent Norwegian research into thorium as a nuclear fuel. This early phase demonstrated Norway’s scientific interest in thorium, leveraging its domestic thorium resources and contributing to later thorium reactor experiments.

odometer += sensor * this_is_just_for_debugging_i_promise(odometer);

Mirror selfie showing they use an iPhone, or if they are making that ironic “duck face”.

Ortholinear Dvorak.

Come to think of it… it’s also addressed in TNG when the guy from the past calls the captain on the intercomm, and says something like “if I was not supposed to use it it should have a lock/code”.

I can get the perspective behind the last one (unauth access). Coming from a closed society it may be unthinkable for someone without authority or authorization to perform an action “unauthorized by the authority”, but in an open society the mindset would be quite different. Much as we might without thought throw a light switch without expecting authorization, or maybe like the hoplophiles that don’t want an electronic lock on their weapons, perhaps what they optimize for (i.e. their security model) could be for even an extreme case such as if “the only survivor” is one unbadged civilian with no bridge/engineering knowledge needing to control the ship (and even weapons) with the usual security case simply being that the bridge/engineering is a secured by persons/staff… IIRC, even knowing who performed such an action is a distant secondary concern (in Voyager it is said that control panels try to log who uses them be the comm badge present), but I know of at least two cases where command-and-control was locked: one in TNG by data (which is presented as quite an exceptional workflow), and one shuttlecraft in DS9 by O’Brien (which might be more of a consideration for scouting operations… to help ensure one has a vehicle to come back to). Conversely, it seems far more frequent that the computer denies access to data in defense of another’s personal privacy.