You're not alone on this, I've also felt the same way, and those knowledge often lives in people's heads or random slack threads, and with AI code it's even worse It just generated what looked reasonable at the time.
reply> Just getting the code to run on your laptop took a week.
replyThis one surprised me. Claude Code in the CLI has made standing up an app and debugging whatever random dependencies or docker BS a dream compared to the before times, when you'd have to learn the architecture while simultaneously troubleshooting whatever isn't working on your machine
And in the before times, you learned a lot and walked away with knowledge on the deps needed, connections, .env secrets, and cleaned it all up and documented it so the next dev would have an easier time doing it.
replyYeah, that totally didn't happen the majority of the time.
replyYes it did. That's how I learned a great many things throughout my career. I'm sure some people didn't pay attention or try to understand what they were doing, and didn't learn. That's on them. But most of us learned a lot that way.
replyBullshit I just pasted random shit from google in until it worked and then instantly forgot which combination of the 20 things I tried got it there.
replyIndeed, there were plenty of people doing just that. I imagine they get the most out of vibe coding. However, when it became a problem, an engineer was still required to fix it.
replyIt might have been you, a couple of months later, or someone else. I have dealt with slop produced by unknowing programmers most of my career. With this vibe coding I think my job is still safe. The amount, though, is increasing exponentially.