196
Vibe-coded build system NX gets hacked, steals vibe-coders’ crypto (pivot-to-ai.com)
submitted 1 year ago by [M] to c/techtakes@awful.systems
23 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 1 year ago (1 child)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 1 year ago*

    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.

  • permalink
  • fedilink
  • source
  • parent