Programmer Humor

Seriously, has no one heard of sandboxing?

Having working production database config and credentials in your local .env, as appears to be the case here, is equally wild, and basically begging for something like this to happen.

That takes me back to 2004

No Smoke, by unknown,

Tech: "Hello. How can I help you today?"

Customer: "There's smoke coming from the power supply on my computer."

Tech: "Sounds like you need a new power supply."

Customer: "No, I don't! I just need to change the startup files."

Tech: "Sir, what you describe is a faulty power supply. You need to replace it."

Customer: "No way! Someone told me that I just had to change the system startup files to fix the problem! All I need is for you to tell me the right command."

(Ten minutes later...)

Tech: "Well, we don’t normally tell our customers this, but there's an undocumented command that will fix the problem. Add the line "LOAD NOSMOKE.COM" at the end of the CONFIG.SYS file and everything should work fine."

(Five minutes later...)

Customer: "It didn’t work. The power supply is still smoking."

Tech: "Well, what version of Windows are you using?"

Customer: "Windows 98."

Tech: "Well, that's your problem. That version of Windows doesn't include NOSMOKE. You'll need to contact Microsoft and ask them for a patch."

(When nearly an hour had passed, the phone rang again...)

Customer: "I need a new power supply."

Tech: "How did you come to that conclusion?"

Customer: "Well, I called Microsoft and told the technician what you said, and he started asking me questions about the make of the power supply."

Tech: "What did he tell you?"

Customer: "He said my power supply is not compatible with NOSMOKE."

What should I call it then?

How do you achieve that? Calling it out when it happens?

I don't like LLMs outside of debugging and the way it mimics human closeness creeps me out

It puts the lotion in the basket

just doesn't roll from my tongue that easily like "you"

Ignorance is bliss.

Prod should always be highly "air gapped" with some sort of deployment process which tests not only the code to be deployed but also the deployment itself. I've been doing QA for a good while now, and everywhere I've worked has testers dedicated to testing the actual update process to make sure it will be safe when deployed.

Having production credentials in a dev environment is more stupider but they'll never learn because they outsourced their thinking.

Creating an environment that incentivizes not thinking is peak stupid.

The bad news for them is that AI is terrible at getting it 'right' the first time, so they have to do things over and over again guessing until it works. So the AI-heavy user pretty much has to just let the commands run to get any benefit since otherwise it's spending 95% of its time waiting on user to approve commands. Further, it's likely commands the user doesn't understand, because they are asking AI to do it in the first place frequently because they don't know themselves.

I'm with you, but as a result other people proclaim to be 'better' AI users largely because they trust the AI. Their stuff is crap and once in a while one of them blows themselves up, but in the short term they are getting praise from management.

Man I can't wait for the bubble to pop and management no longer being hyped for the sake of hype over it.

"Make no mistakes"

As if the LLM can truly understand what a mistake is...