Comment by imiric

Fair enough. There are valid use cases for vibe coding scripts and simple CRUD apps, which current AI tools are fairly competent at producing.

The thing is that those don't typically take weeks and months to build with conventional tooling. And I find it hard to believe that all you're doing is this type of integration work. But I suppose there are companies that need such roles.

> There are companies out there that make millions, in areas you‘ve never heard of, and their core business does not depend on software development best practices.

That is true.

I do think that this cowboy coding approach is doing these companies a disservice, especially where tech is not their main product. It's only creating more operational risk that on-call and support staff have to deal with, and producing more technical debt that some poor soul will inevitably have to resolve one day. That is, it all appears to work until one edge case out of thousands brings down the entire system. Which could all be mitigated, if not avoided, by taking the time to understand the system and by following standard software development processes, even if it does take longer to implement.

What you describe isn't new. This approach has existed long before the current wave of AI tooling. But AI tools make the problem worse by making it easier to ship code quickly without following any software development practices that ensure the software is robust and reliable.

So, it's great that you're enjoying these tools. But I would suggest you adopt a more measured approach and work closely with those senior and junior engineers, instead of feeling like a wizard from the future.