right the product people won't care or won't know so the LLM will just spit out whatever. to the product people it'll look legit and make sense. once it's handed to a dev in most cases it might as well just be thrown out of the window. so it's pointless. it'd be easier/faster to just cut out the middle man, the AI, and go directly to the dev and have the product people tell them exactly what they want/need.

That's because the joke got updated to the newest OS version until CONFIG.SYS got entirely removed in Windows ME and it just didn't work any more.
It's originally from MS-DOS times. Earliest telling of it I know of is from 1996.

The 60's happened in the 70's.

The 70's happened in the 80's.

You get where I'm going here?

Are you under the impression that everytime someone comes inside a woman that woman becomes pregnant, and that this can only happen one time in a woman's life?

Either that, or by "unhealthily", maybe he was obsessed with this kid's channel so much he went out and seduced the kid's mom as some kind of display of ultimate dominance, maybe using "I just got my pilot's license" as an opener.

...Or yeah his kid who he conceived when he got his pilot's license is now half his age and runs a YouTube channel, and excessive YouTube is unhealthy by default. . .maybe that one's more likely. 😂

Unhealthily watching = scrolling shorts for too long.

Well nowadays there is "someone else" (for a given definition of "someone") with a set of controls. Kids are being taught to drive in machines that literally drive themselves, and they need to learn that every decision that the self-driving computer makes ultimately falls on them as the driver. I think they were saying that this is a concept that needs to be taught, not a law that needs to be enacted.

That's not to say that a manufacturer is blameless when a FSD car careens into the side of a building at 80 mph. Just that immediate legal responsibility for the movement of a vehicle generally falls on a driver.

The concept absolutely exists in law but it’s just called… “the driver.”

There's another aviation term, "The Pilot Flying." The Pilot In Command bears the authority and responsibility. The Pilot Flying is doing the work of steering. If present, a Pilot Not Flying might help with checklists, system monitoring, navigation, radio communication, handling secondary controls like flaps and landing gear, but the Pilot Flying is in immediate control of the aircraft.

The PIC is very often not the pilot flying. I used to be a flight instructor, when teaching students who aren't yet qualified to command, I acted as Pilot In Command, but the student was the Pilot Flying as much as possible.

Autopilots have been a thing for most of aviation history. It doesn't count as a crewman. It's a piece of equipment like any radio or gauge. It is a tool at the PICs disposal. It is the PIC's job - sometimes delegated to the Pilot Flying - to monitor the autopilot and take over if it begins doing something wrong.

That's the concept that is missing with self-driving or driverless cars. Tesla drivers will sit in the driver's seat and abdicate command of the vehicle to the autopilot, or worse, cars are operating as taxis with passengers in the back seat and no one in the front seat, or with no onboard controls at all. Fully autonomously, or remotely operated by Southeast Asians who...totally have a valid American driver's license. Definitely.

Corporations love it. "Legally, the driver is responsible for the vehicle. Our car has no driver, so legally no one is responsible for the vehicle. Responsibility averted."

The concept is that anything that happens to that aircraft (or car) is the sole responsibility of the pilot. Flying into restricted airspace? If it's necessary to avoid a collision, you do it. Putting the plane down in a field? Better than hoping you can make it to a runway when your engine is out and lives are on the line. Another driver signals that you are clear to make a left turn on a congested road? Nope, because when that traffic you couldn't see hits you on the right, you're responsible for your car, their car, and all the people inside both vehicles.

Of course they do. It's even mounted rw at the root of the AI drive for ease of access in case something goes wrong.

I hope they dont so that it hurts and they maybe learn

Prod deployments should come from a build server though and if you're deploying multiple times a day you should have a well built CI pipeline to handle it.

Remoting into a management server would still have people using an account on the management server and their personal db login credentials.

We also don't give devs write access to production and all scripts run in production are run by our DBA after they have been approved by the lead Dev, operations and the DBA.

This might be overkill for some systems, but we won't ever accidentally delete our prod data. Our system requires this level of scrutiny due to the nature of our systems.

that is absolutely NOT the way that works in any functional environment

your ability to deploy quickly comes directly from your automation, and those automation tools - NOT developers - have the secrets in them

deploy to prod multiple times per day isn’t some win by itself… the ability for large teams (not 1 fuckwit and a goon squad of agents) to deploy without breaking things and in ways that are safe is the win here… anyone can deploy to prod multiple times per day… but anyone isn’t netflix (the originators of the “multiple times per day” line) with the uptime they achieve over years while doing it