6 ms·

This is literally the recipe for the coming software apocalypse. Just watch the software engineers who say "Let's be careful" lose their jobs and get replaced

This is literally the recipe for the coming software apocalypse. Just watch the software engineers who say "Let's be careful" lose their jobs and get replaced by non-technical vibe-coders churning out 10K lines of dirty insecure, unmaintainable code per day... Ticking time bomb. I swear, good engineers are going to move to North Korea to monetize because of the amount and size of 'opportunities' this will create. It seems so far-fetched but that's the direction it seems to be heading.

yhcj 9d ago
exactly how I feel. I mean let's face it, we were overpaid and underworked because we were considered magicians, but the magic is gone. What I fear is that it's impossible for the untrained to see the difference between a highly-technical developer and the vibe-coder. Software is so buggy nowadays (just look at Facebook, or Facebook Ads. Crazy) I wonder what's going to happen in the long run. I was banking on the opportunities it will create but nah, have you tried debugging AI-generated codes of thousands of lines where the original dev doesn't exist? It's a mess I don't wanna clean up.
- socketcluster 8d ago
  >> I was banking on the opportunities it will create but nah Seems we're on the same wavelength because I had the exact same thought about this. But actually, I'm probably not so fussy. I wouldn't mind cleaning up the mess if I'm paid hourly... But now my concern is: What if they want me to clean up the mess but demand that I do it in a particular way which makes it impossible? I'm already seeing signs of this. This was already kind of the case in my last job; I had to fix things and implement new features but we had to keep the same clunky, over-engineered architecture. My current job doesn't have the same degree of architectural legacy baggage but there is a lot of bureaucracy to deal with instead, which is itself restrictive.

yhcj 9d ago

exactly how I feel. I mean let's face it, we were overpaid and underworked because we were considered magicians, but the magic is gone. What I fear is that it's impossible for the untrained to see the difference between a highly-technical developer and the vibe-coder. Software is so buggy nowadays (just look at Facebook, or Facebook Ads. Crazy) I wonder what's going to happen in the long run. I was banking on the opportunities it will create but nah, have you tried debugging AI-generated codes of thousands of lines where the original dev doesn't exist? It's a mess I don't wanna clean up.

socketcluster 8d ago
>> I was banking on the opportunities it will create but nah Seems we're on the same wavelength because I had the exact same thought about this. But actually, I'm probably not so fussy. I wouldn't mind cleaning up the mess if I'm paid hourly... But now my concern is: What if they want me to clean up the mess but demand that I do it in a particular way which makes it impossible? I'm already seeing signs of this. This was already kind of the case in my last job; I had to fix things and implement new features but we had to keep the same clunky, over-engineered architecture. My current job doesn't have the same degree of architectural legacy baggage but there is a lot of bureaucracy to deal with instead, which is itself restrictive.