4 ms·

I made a quick throwaway to share my anecdote. I'm at a YC company. We have a dev team < 15 engineers. We all expressed concerns about going full vibe coding

I made a quick throwaway to share my anecdote. I'm at a YC company. We have a dev team < 15 engineers. We all expressed concerns about going full vibe coding, so the technical co-founder hired a bunch of vibe coders and has them on a private "SEAL team" building vibe coded monstrosities without any regard to safety, integrating with our main product, hosting consistency, or anything else. I don't know if this is anyone else's experience. But I'm WAY more concerned about vibe coding than others seem to be just due to my proximity to the nonsense.

Nikolay_p 1y ago
the founders think they can do it without any real developers, they will fail. But you have a bigger problem, the tech co-founder (CTO) is an idiot, that company is not going anywhere.
tuckerman 1y ago
Sorry you have to deal with that and I hope they see the ramifications of their decision soon, but if this is your technical co-founder I'd recommend looking for a new role. Can you share more about what the workflow of this new team looks like? I consider myself a strong proponent and heavy user of AI tools for development but it's still hard for me to fathom how true "vibe coding" at this scale is possible.
- throw-vibec0d3 1y ago
  My founders are certainly already in this thread, so I don't want to say a whole lot more. The more specific I get, the increased likelihood I get called in for a chat today for being "unwilling to adapt." But it's far worse than you're probably expecting from a company with good investors and revenue. I expect things will go terribly wrong very soon. The PM just decided they didn't want to queue up tickets or designs anymore, so they're on this vibe coding team. We aren't even in interviews with devs going onto that team, though you can hardly call them devs (Maybe that's elitist of me. but that's how I'm feeling.) And sorry this is turning into a therapy session, but all of us devs actually like AI tooling. We're getting decent to good value out of claude code and the like. We've implemented a fairly neat little MCP for our CS team to use as a walled-garden admin tool. And yet, since we criticize things, we're branded as "non-believers" and the implication is that we are impeding the company's growth. Suffice it to say, all us career devs are already interviewing and on our way out here.

Nikolay_p 1y ago

the founders think they can do it without any real developers, they will fail. But you have a bigger problem, the tech co-founder (CTO) is an idiot, that company is not going anywhere.

tuckerman 1y ago

Sorry you have to deal with that and I hope they see the ramifications of their decision soon, but if this is your technical co-founder I'd recommend looking for a new role. Can you share more about what the workflow of this new team looks like? I consider myself a strong proponent and heavy user of AI tools for development but it's still hard for me to fathom how true "vibe coding" at this scale is possible.

throw-vibec0d3 1y ago
My founders are certainly already in this thread, so I don't want to say a whole lot more. The more specific I get, the increased likelihood I get called in for a chat today for being "unwilling to adapt." But it's far worse than you're probably expecting from a company with good investors and revenue. I expect things will go terribly wrong very soon. The PM just decided they didn't want to queue up tickets or designs anymore, so they're on this vibe coding team. We aren't even in interviews with devs going onto that team, though you can hardly call them devs (Maybe that's elitist of me. but that's how I'm feeling.) And sorry this is turning into a therapy session, but all of us devs actually like AI tooling. We're getting decent to good value out of claude code and the like. We've implemented a fairly neat little MCP for our CS team to use as a walled-garden admin tool. And yet, since we criticize things, we're branded as "non-believers" and the implication is that we are impeding the company's growth. Suffice it to say, all us career devs are already interviewing and on our way out here.