If you are developing software with financial impact, and every developer downloads their dependencies from the internet without further checks, you already have set up yourself for desaster.
If you would ask a LLM for how to guard yourself against malicious dependencies, this would be one of the first things they’d point out.
Yeah, just doing shit without worrying about things like security is a core part of vibe coding. Vibecoding as a concept put into practice is definitely to blame.
I think the same “professional” environment where whomever made the decisions for systems architecture thought that Production systems that deal with a shitton of money should be in the same network as machines which aren’t locked down like crazy and whose users can install whatever the fuck they want, is the kind of environment where people thinks vibe coding is great.
If you are developing software with financial impact, and every developer downloads their dependencies from the internet without further checks, you already have set up yourself for desaster.
If you would ask a LLM for how to guard yourself against malicious dependencies, this would be one of the first things they’d point out.
Also crazy how they are just allowed to “indulge” themselves with vibecoding on a machine that can access live production servers.
Yeah, just doing shit without worrying about things like security is a core part of vibe coding. Vibecoding as a concept put into practice is definitely to blame.
I think the same “professional” environment where whomever made the decisions for systems architecture thought that Production systems that deal with a shitton of money should be in the same network as machines which aren’t locked down like crazy and whose users can install whatever the fuck they want, is the kind of environment where people thinks vibe coding is great.
Incompetent idiots leading incompetent idiots.
If you don’t know enough to write the code yourself, you likely also don’t know enough to ask the right questions