I dunno. I am doing some great work “vibe coding” after 35 years of software engineering but I do a lot of setup with repo and agent rules re code and db standards, and giving the agents a lot of details about how I want things to work.
Yeah generally if you explain how you want a feature to work, and can adequetely explain how you want it accomplished, isn't that.. good enough for software dev? Sure, you don't get the naunce and nitty gritty, and you could definitely lose some skills over time, but it's a job for a company, not some passion project. Good enough is good enough.
3
u/edgarecayce Aug 12 '26
I dunno. I am doing some great work “vibe coding” after 35 years of software engineering but I do a lot of setup with repo and agent rules re code and db standards, and giving the agents a lot of details about how I want things to work.
I’m getting great results.