@psen102 Don't think so, I am working in a startup and when it's my turn I make sure to reply to people, even late at night, atleast for the features I have made
Why you still cannot trust Vibe coding in production systems:
Yesterday I was working on a particular service written in GO, I let AI write several background jobs.
The code worked. The jobs ran. Tests passed.
But when I actually analysed what those jobs were doing to our production systems, the numbers were ridiculous.
-~89.6k Service calls/hour โ ~180 bulk calls/hour.
- an unnecessary 18-hour wave of processing.
- ~91k nightly engine calls โ ~206 stores with actual consent activity.
- expensive full scans
I sat down and fixed each one of them reducing the calls by 98% and removing the unnecessary jobs
@NabhaniMehdi interesting, this makes sense, in my case the reason I had to do this in the staging env was because it was part of a big feature and was missed in review
@Priyansh_31Dec I have seen people expecting to ship the features in the minimum time and when something breaks they start asking about the choices we made, but man you didn't even gave the time to research and design a proper arch
@buildwtim tbh it has become an abstraction people don't care about, but if you don't even check the critical things like a DB query, Jobs, etc you are sitting on a time bomb imo