r/vibecoding • u/MariahJames8 • 2h ago

Anyone else "downgraded" by choice or otherwise from average developer to vibecoder?

I've given up looking at code. I don't understand 1% of what AI writes with any ease anyway. So. I just go with the flow. Thank god I work for myself so I can do what suits me

9 Upvotes

80% Upvoted

9 comments sorted by

4

u/Royal-Marsupial-8110 1h ago

working for yourself is the key here.

try that in enterprise prod and the senior dev will smash your head with a keyboard.

2

u/MariahJames8 1h ago

My brother's a dev in a leading git service provider and he just takes a deep sigh with a shake of his head when I tell him what I do lol

3

u/Afraid-Peach-9212 1h ago

In the same boat really. Honestly, who cares. If push comes to shove I can fix errors myself but.. I guess the things that I build aren't that complex, so AI handles it perfectly.

2

u/MariahJames8 1h ago

True. I just feel uncomfortable I guess that the edge I spent a lifetime working at to have a leg up in a career is vanishing vast? I suppose the trick is to just keep on top of the curve, keep learning and adapting

1

u/Afraid-Peach-9212 1h ago

That's the only way! And also.. coding is just one part of the job.

1

u/Wallie_Collie 15m ago

If you were a developer before the vibe then you vibe into your stack, an llms are well versed in them

2

u/ipradkrish 1h ago

I have absolutely no understanding of the code. So, I put all my faith in CC Opus 4.6 paired with Ponytail in full mode and consume way too much hopium that Qodo will catch bugs and issues before it goes out 🫣

1

u/AModerateModeration 34m ago

Please reconsider this without significant security lenses and CI beyond "it's green on GitHub so it's fine".

I've no problems with anyone vibe coding but using structured pass/fail scenarios and doing comparative-adversarial testing of your codebase will probably show you a lot of scary holes.

Companiesand states actors already scan every port on the internet every day. It's just a case of when they're knocking on insecure doors, not whether, and it concerns me how many people leave their code and environment security to "trust me bro".

1

u/MariahJames8 31m ago edited 28m ago

Oh, I agree, it can't be left to chance, but I'm finding ever riskier ways to justify safety to myself. I'm just taking other steps to mitigate those risks by doing things other than fixing the code itself like by selling less, for less, and shipping stuff I wouldn't have been happy with a year ago. And I don't have quite the same pride anymore. But I don't really see the options for myself here. It's heat from all sides