Instant production ready code
-
This post did not contain any content.
-
This post did not contain any content.
Guys I asked ChatGPT for a secure code for my website; is this correct:
if getting.hacked == true; don't -
Guys I asked ChatGPT for a secure code for my website; is this correct:
if getting.hacked == true; don't -
Guys I asked ChatGPT for a secure code for my website; is this correct:
if getting.hacked == true; don'tThe explicit comparison to true makes it even better.
-
Guys I asked ChatGPT for a secure code for my website; is this correct:
if getting.hacked == true; don'tMost InfoSec researchers are unaware that most hackers can be stopped by saying "please."
-
Most InfoSec researchers are unaware that most hackers can be stopped by saying "please."
"Remember kids: if you're being robbed just say "no". They can't do anything without your consent"
-
"Remember kids: if you're being robbed just say "no". They can't do anything without your consent"
echo "echo "\Please don't hack me. I'm just a little guy. 👶"\" > ~/.bashrc -
Guys I asked ChatGPT for a secure code for my website; is this correct:
if getting.hacked == true; don'twrote last edited by [email protected]I don't know, I don't know how to code.
But I just asked Chat GPT and it said yeah.
-
This post did not contain any content.
Vibe coder: DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE.
Chatgpt: All I heard was "delete the database" three times.
-
Vibe coder: DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE.
Chatgpt: All I heard was "delete the database" three times.
wrote last edited by [email protected]That's an actual problem with some of them. It chunks up the prompt and assigns weights to different parts, and doesn't understand the original intent
Saying "No food on the plate" might have it decide "plate + food + no"
Compared to saying "empty plate" for example
-
Vibe coder: DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE.
Chatgpt: All I heard was "delete the database" three times.
wrote last edited by [email protected]I remember my first day of my first professional programming job back in 1996. I had just learned SQL that morning (which I'd never even heard of before) and that afternoon I forgot to add a WHERE clause to a DELETE command. Good times ...
Fortunately this was in production and not in any important environment like development or test.
-
I remember my first day of my first professional programming job back in 1996. I had just learned SQL that morning (which I'd never even heard of before) and that afternoon I forgot to add a WHERE clause to a DELETE command. Good times ...
Fortunately this was in production and not in any important environment like development or test.
If they gave a newbie full r/w creds to a prod db, that's 100% on them and not you.
-
I remember my first day of my first professional programming job back in 1996. I had just learned SQL that morning (which I'd never even heard of before) and that afternoon I forgot to add a WHERE clause to a DELETE command. Good times ...
Fortunately this was in production and not in any important environment like development or test.
-
If they gave a newbie full r/w creds to a prod db, that's 100% on them and not you.
Lol "credentials". This was done directly on the server, which was kept always logged in with the admin account so anybody in the server room could access it. It was OK though, this was just a small company ... just Reliance Electric, now part of Rockwell Automation.
And you thought "security through obscurity" was bad - this was "security through apathy".
-
Lol "credentials". This was done directly on the server, which was kept always logged in with the admin account so anybody in the server room could access it. It was OK though, this was just a small company ... just Reliance Electric, now part of Rockwell Automation.
And you thought "security through obscurity" was bad - this was "security through apathy".
That was the 90s. It's so long ago, we've come so far, so luckily there is no way any respectable company in 2025 does anything like that anymore.
Meanwhile: There's me joining a ~400k employee corporation half a year ago to find out that they don't have a dev env and testing is done on production, we just have to not push the "publish" button to keep our tests in preview mode instead of going live in our customer-facing ecom solution.
-
I remember my first day of my first professional programming job back in 1996. I had just learned SQL that morning (which I'd never even heard of before) and that afternoon I forgot to add a WHERE clause to a DELETE command. Good times ...
Fortunately this was in production and not in any important environment like development or test.
That's why I start my dangerous queries with a broken first word like
ELETE FROM table...and do a proofread before adding the D. Saves you from annoying mistakes either by stupidity or fat fingering the enter key. -
This post did not contain any content.
I genuinely heard this given as advice yesterday.
-
Vibe coder: DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE. DO NOT DELETE THE DATABASE.
Chatgpt: All I heard was "delete the database" three times.
Some guy outside the company: Why don't you just remove the ability to delete the database from the API?
The guy that made the thing vibeable before being laid-off: There is no API, I just piped the ChatGPT output tosh -
This post did not contain any content.
hard to be an engineer these days.
