That’s honestly technology in a nutshell. Technological development leads to further abstraction, leading to less low level knowledge. It’s always been this way. Is AI an abstraction step too far, or are we just the next generation of old man yelling at cloud?
When cloud first became a thing I yelled at the cloud a lot. Then I got on board with provisioning. And they stepped up the game with load balancers that actually have features security groups SSL unwrapping.
No I realize that one person with a cloud account can do the work of three or four of system engineers.
If you know what you’re doing, you can definitely do this hybrid of vibe coding and real coding. You can’t just give it a problem and tell it to solve it you need to tell it exactly what you’re expecting it to do. Occasionally you can ask it if it has any suggestions and it’ll come back with something that you didn’t think of that’s not a half bad idea.
That said, there’s a lot of idiots out there with zero skill just vibr coating stuff they have no business doing leaving vulnerabilities and caution to the wind.
Before AI we used to refer to the “vibe coders” as “script kiddies”. People who would find a chunk of code and apply it to a job without really knowing what it did.
Fine when they were working alone and what they were up to wasn’t your problem. But as soon as you got into a team project, the code base would start filling up with these patchwork, confused, inefficient solutions to systemic problems.
You’d have the same bug in three different places and you’d have to run down the flaw over and over again, because someone was just copypasta-ing a solution wherever it would fit.
That’s honestly technology in a nutshell. Technological development leads to further abstraction, leading to less low level knowledge. It’s always been this way. Is AI an abstraction step too far, or are we just the next generation of old man yelling at cloud?
I asked myself that question a lot.
When cloud first became a thing I yelled at the cloud a lot. Then I got on board with provisioning. And they stepped up the game with load balancers that actually have features security groups SSL unwrapping.
No I realize that one person with a cloud account can do the work of three or four of system engineers.
If you know what you’re doing, you can definitely do this hybrid of vibe coding and real coding. You can’t just give it a problem and tell it to solve it you need to tell it exactly what you’re expecting it to do. Occasionally you can ask it if it has any suggestions and it’ll come back with something that you didn’t think of that’s not a half bad idea.
That said, there’s a lot of idiots out there with zero skill just vibr coating stuff they have no business doing leaving vulnerabilities and caution to the wind.
Before AI we used to refer to the “vibe coders” as “script kiddies”. People who would find a chunk of code and apply it to a job without really knowing what it did.
Fine when they were working alone and what they were up to wasn’t your problem. But as soon as you got into a team project, the code base would start filling up with these patchwork, confused, inefficient solutions to systemic problems.
You’d have the same bug in three different places and you’d have to run down the flaw over and over again, because someone was just copypasta-ing a solution wherever it would fit.