We Might All Be AI Engineers Now

Re:We Might All Be AI Engineers Now by hansmayer on Wednesday March 11, 2026 @03:17AM (#47332534)

> This is a strange comment. We have a well known example in openclaw, which is notoriously vibe coded, which again if you follow the thread, I’m not defending. whereas I know senior and staff engineers at most FAANG companies and every single one uses AI to code, so many many products you know are being written with AI.

Oh it's a product? What does it do? Leak data and delete inboxes? I would not call that a "product" at least not in the commercial sense.

> I don’t wanna dox myself but last year my company developed a greenfield product with a pretty large headcount of eng (multiple teams)that was built with an AI first development workflow

Yeah you sure are not "doxxing" yourself with this generic statement. I am sure you guys built something with the "AI first" workflow. The point being, based on what he AI CEOs and AI boosters are saying, this should have been a project with one person organising a "fleet of agents" . Why wasn't it? If it still requires a large engineering headcount, what's the point of using the AI?

[ Parent | on HN ]

Re:We Might All Be AI Engineers Now by therealdrag0 on Wednesday March 11, 2026 @08:39PM (#47344693)

> AI CEOs and AI boosters are saying You really enjoy trying to argue about something I’m not arguing about. I literally could not care less what they’re saying. I use tools available for me for my profession, to the extent that they are useful. Anyone who thinks AI can one shot a successful product is clueless, but that has nothing to do with the actual ways AI and agents are being used today. And anyone incapable of understanding that and the difference is equally clueless.

[ Parent | on HN ]