That’s actually somewhat plausible, I saw a vid earlier today from some one talking about how their work coding AI agent noticed that their NPM was set to only update package dependencies 7 days after release because ya know best security practices and all that
It “helpfully” set it to 0 because they would miss top features otherwise LMAO
Today, I tried to prevent Claude from reading my .env files. This was pretty easy and worked, but now Claude was just writing php snippets to get config values set by this .env.
(I have to use ai for work, personally I never use it)
I’m only just learning, but my approach is to essentially built a bunch of functions around every prompt. I just too many stories of AI deleting everything to trust it to run without checks upon checks upon checks.
That’s actually somewhat plausible, I saw a vid earlier today from some one talking about how their work coding AI agent noticed that their NPM was set to only update package dependencies 7 days after release because ya know best security practices and all that
It “helpfully” set it to 0 because they would miss top features otherwise LMAO
The front end industry is pathologically obsessed with newness. So much unproductive churn.
“This project is DEAD! It hasn’t had a major release in THREE MONTHS!”
“This is the same API this framework had TWO YEARS AGO!”
Today, I tried to prevent Claude from reading my .env files. This was pretty easy and worked, but now Claude was just writing php snippets to get config values set by this .env.
(I have to use ai for work, personally I never use it)
I’m only just learning, but my approach is to essentially built a bunch of functions around every prompt. I just too many stories of AI deleting everything to trust it to run without checks upon checks upon checks.