4w ago

Vibe-coded build system NX gets hacked, steals vibe-coders’ crypto

pivot-to-ai.com Vibe-coded build system NX gets hacked, steals vibe-coders’ crypto

NX is build software. You write your code on your laptop, you press “build”, it runs NX, and you get a built version you can put onto your web server. If you could hack NX, you could hit a lot of p…

a clown car of clown cars that deploys another clown car, that explodes

https://www.youtube.com/watch?v=vnFKkBBzpVg&list=UU9rJrMVgcXTfa8xuMnbhAEA - video
https://pivottoai.libsyn.com/20250829-vibe-coded-build-system-nx-steals-vibe-coders-crypto - podcast

Not The Onion @lemmy.world

Vibe-coded build system NX gets hacked, steals vibe-coders’ crypto

pivot-to-ai.com /2025/08/29/vibe-coded-build-system-nx-gets-hacked-steals-vibe-coders-crypto/

398 40

Lobste.rs @lemmy.bestiver.se

Vibe-coded build system NX gets hacked, steals vibe-coders’ crypto

pivot-to-ai.com /2025/08/29/vibe-coded-build-system-nx-gets-hacked-steals-vibe-coders-crypto/

14 0

You're viewing a single thread.

23 comments

I know it's been said thousands of times before, but as a software developer I've never felt a greater sense of job security than I do right now. The amount of work it's going to take to clean up all this slop is going to be monumental. Unfortunately, that kind of work is also soul-deadening.
- Just vibe code a solution, and then when that goes wrong vibe code the solution to that. Should keep you in work for decades.
- A lot of companies use "vibe coding" an excuse to offshore software development work to cheaper countries without anyone noticing.
  But yeah it's not gonna work out in the long term for a business that:
  Encourages people to submit random nonsense to the codebase instead of doing actual work
  Removes all entry-level positions
  Lays off anyone who knows what they're doing
  That's how you get a codebase that kinda sorta works in a way but is more evolved than designed, full of security holes, slow as heck, and disorganized to the point where it's impossible to fix bugs, adds features, or understand what's going on.
  
  That’s how you get a codebase that kinda sorta works in a way but is more evolved than designed, full of security holes, slow as heck, and disorganized to the point where it’s impossible to fix bugs, adds features, or understand what’s going on.
  Well, one of the ways glancing at the code I'm responsible for, sweating profusely
  
  Yeah, idk what parent poster is talking about. I totally didn't spend the bulk of yesterday afternoon redoing a small project from scratch because I couldn't decipher what I did two months ago. Nope. That would be ridiculous! So glad my human-written code is so much better than AI code.
- At a new job I asked about the crash rate of the mobile app during the interview, and they brought up a dashboard showing it was very low. I wasn't paying enough attention, but they were showing me the daily crash rate, and the day rolled over in UTC time, and had apparently just rolled over in the middle of our day, so not a lot of crashes yet. It actually had an abysmal crash rate. Structured / designed poorly at the core.
  Fixing that app took years. Some of it was definitely soul deadening, but there was also something good about turning it all around and people seeing the positive impact as things kept getting better.
  
  I like tackling a spaghetti garbage dump of code, and bringing it some structure and crash resistance.
  
  It can be good, but depending on how much it is, can get pretty monotonous fixing the same problem repeatedly. This was a multi year thing in this case.
  
  Hopefully you at least got some measure of free reign with it. The main times I find cleanup jobs soul-destroying is when I'm getting micromanaged or otherwise harassed by clueless managers.
  But given space to breathe and work, I often enjoy tidying up code messes. Gives me the same sensation as when I used to rewire spaghetti data closets in college.
  
  Ya, they let me do it how i wanted and I mostly got to choose what I'd work on next for the clean up task.
  It was great to start, but it's size just eventually made it tedious. Oh, I'm doing this again, and I know exactly what my week is going to look like, because the other screen I just did is wrong in exactly all the same ways from top to bottom.
  If a new feature was needed in an area and it wasn't urgent I'd say I'm fixing that area first, and then make the new feature. If there were serious bugs that needed fixing, unless it was a easy hotfix with other priorities, I'd fix that whole area instead first.
  Edit: Watching the crash rate tick down with all the progress though was great.
- It reminds me of the people still being paid to clean up or maintain the large Fortran and COBOL codebases
- By my guess, its gonna take about a decade to fully clean up the mountains of slop code that this AI bubble's gonna leave. It'll certainly be lucrative (and soul-deadening, as you note), but as someone else has noted before, the riches are exclusively going to experienced devs and senior programmers - for anyone trying to break into the industry, they're probably gonna have to find work somewhere else.
- I wish I could agree, but I was one of the countless laid off to make way for our new overlords

23 comments