2

If you're not vibe coding you're going to be left behind?

Profile picture
Mid Level SWE at Taro Community2 months ago

https://x.com/garrytan/status/1897303270311489931

For 25% of the Winter 2025 batch, 95% of lines of code are LLM generated.

And they go on to say that if youre not vibe coding youre going to be left behind.

Vibe coding is basically just hitting accept all on cursor and just going with the vibes

How should we be interpreting this? are they correct here?

468
5

Discussion

(5 comments)
  • 3
    Profile picture
    Tech Lead/Manager at Meta, Pinterest, Kosei
    2 months ago

    For the uninitiated, here's what vibe coding means (from Wikipedia):

    Vibe coding is an AI-powered programming practice where a programmer describes a problem in a few sentences as a prompt to a LLM tuned for coding, while ignoring the details of the generated code.

    (So interesting how terms catch on...)

    Vibe coding could make sense in a startup environment when a lot of what you build is throw-away prototypes anyway.

    But in larger tech companies, you must know things work at a deep level. Your value lies in mastery of a specific domain or technology. This is especially true for a junior developer.

    The difference is:

    • In Big Tech, you are working on a team, and your ability to be the go-to person for something is incredibly valuable. You can't hand wave the internals of a component you're working on.
    • Maintenance is paramount in Big Tech, since the code you write might live on for years and many people may extend or modify your code. Until we get to the point where AI tools are able to reason through this and make further modifications (i.e. we hand over the full reins to AI), we cannot afford to ignore the internals of AI code.
  • 2
    Profile picture
    Startup Engineer
    20 days ago

    It's a made-up term, but I feel like people are equating "vibe coding" to "YOLO coding." My take is that the effectiveness of using AI assist is going to be wholly dependent on the developer, based on their familiarity and experience (their "vibes" on what they see the AI spits out) with whatever they're working on.

  • 1
    Profile picture
    Employee @ Robinhood
    2 months ago

    It's just sales and hype: a lot of it is just exaggreration to get people to use AI more so AI company evaluations and hype.

    I tried using AI tools to write CrowdStrike QL and it was not super helpful. I don't know about vibe coding, but I spent the entire time complaining out loud how much it sucked.

  • 1
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    2 months ago

    I like Garry Tan, but he has some... weird takes sometimes. Remember that he literally runs the biggest startup accelerator on the planet, so it's in his best interest to drive the AI narrative.

    That being said, I wouldn't be surprised if these numbers were true (i.e. not cherry-picked/stretched/distorted). YC focuses on very early-stage startups, and when you're just starting out, it makes sense to quickly generate a bunch of throwaway prototype code.

    As Rahul mentioned though, generating 95% of your code with AI won't fly in any larger company. Even at Series A, you're generally going to have some sort of technical debt and certain contextual roadblocks that AI will struggle to work around. You will also have some amount of traction at that stage, so you can't just hit full send on risky AI-generated code. It's been 2+ years since ChatGPT came out, and I still 100% believe that the skills in this course (skills that AI are absolutely terrible at) are extremely valuable: Level Up Your Code Quality As A Software Engineer

    Here's another fun thread about AI coding: "ZUCK will replace mid level engineers with AI"

    • 1
      Profile picture
      AI/ML Eng @ Series C startup
      2 months ago

      Heck even at seed stage... most of the time, the existing code wouldn't have handled all the common cases. Then when you say "Refactor this code for me", Claude slashes up your code even more.