HorrorVC | AI Confessions
29 posts

HorrorVC | AI Confessions
@horror_vc
how AI impacts us with no bs. anonymous vibe coding confessions.
SimCity Katılım Ağustos 2025
15 Takip Edilen114 Takipçiler

hired as a 'senior dev' at a startup. they don't know 90% of my output is Claude Code with me directing it, sorry ORCHESTRATING. delivered sprint after sprint, got employee of the month, got a raise, the code runs fine, the tests pass. this is the job now and based on my expectations I'll be able to completely replace myself with an avatar
English

I WAS THE VP OF ENGINEERING. I PUSHED FOR VIBE CODING AND CONVINCED THE CEO. I SAID IT WOULD CUT OUR RUNWAY IN HALF AND IT DID. WE SHIPPED FASTER THAN EVER AND THEN WE LAUNCHED AND EVERYTHING BROKE AND WE LOST OUR THREE BIGGEST ENTERPRISE CUSTOMERS IN TWO WEEKS. I was walked to my car by security on a thursday afternoon. dont be me
English

This is totally "made up" story. Sold my saas for 2.1 million, buyer from singapore did six weeks of due diligence - analytics, revenue, churn, blah blah blah, very thorough. Never once asked how long it took to build (3 days + Claude code lol). I told it what I wanted and deployed whatever it gave me. Never read a single line. The entire backend is raw unreviewed AI output. I signed the deal in a room with nine people and I havent stopped shaking since
English

ok so funny story. i used GPT-4 to build a trading bot. gave it full access to my binance account. told it to "be aggressive." it was. lost 34k in 11 hours. the bot was doing something with leverage i still dont understand. support told me it was working exactly as designed. bro i had designed nothing, you did that. i had just typed words into a chat box and connected it to my life savings.
English

The API rate limiting logic that Codex generated was wrong in a very specific way: it rate limited per API key, but the keys were rotating automatically. Effectively no rate limiting at all. Our competitor found this. They scraped our entire product database through the API over one weekend. Every user, every listing, every piece of proprietary data we had. We found out because they launched a competing feature using data that could only have come from us. We have no legal recourse because the data was technically public via the API.
English