Yes, I'm familiar with these talking points. I didn't mention clean code or solid or frameworks or anything like that.

However, the poster explicitly said they don't do what you said (EDIT: I misinterpreted some of these):

RE "talking to customers"

> We get feature requests, improvements, ideas, feedback. JIRA tickets get created, and we ask AI to reference that ticket, code to it, and create a PR

RE "figuring out whether it's actually working for people"

> have senior engineers review the actual functionality and none of them have read any more than a few lines of code

RE "figuring out what the heck to actually build"

> replaced by "vibe" coding

Maybe my definition of vibe coding is wrong?

--

In any case, I don't have some ulterior anti- or pro-AI motive. I'm genuinely curious why and how a project run this way has humans in the loop at all.

Sorry for the confusion, we talk to customers both internal and external that drive these feature requests.

We ultimately decided that paying for low code/no code platforms was pointless because that's what AI coding is. 90% of the time, we don't even have VS Code open and just gloss over the diffs in the PR.

I honestly don't know what the trajectory of those low code/no code platforms are going to look like. Are their senior strategists looking at the landscape in the last year and going "oh. no. What is the point of our product anymore because what's the point of people dragging and dropping no-code connectors to build an application when they can get 100% portability and transparency by having code generated by AI"