‹ BackHN Continuity

Thread

Bend 2 and the Vibe-Coding Trap

327 points · 235 comments · LiamPowell

  1. hmokiguess · · focus · HN ↗
    > The problem is that vibe coding makes it possible to build a substantial solution before learning enough about the problem to recognise that a much better solution exists.

    This example and Bend aside, I find this to be the biggest struggle with the perceived intelligence we have today. It's great at producing something that works, but it is not great at calling you out when you don't know what you don't know.

    It's not able to educate and course correct you unless you have great self awareness and discipline.

    That said, I think this goes for everything, it's easy to fall into this trap because it is very human. We simply don't know what we don't know, so it's not uncommon to revisit an old solution only to be enlightened that there is now new information that allows you to replace it with something much better.

    I don't think anything here is new or changed, if anything changed is really just the rate that we experience this. LLMs make it easier and faster for the feedback cycle to happen.

    Now back to Bend, I think putting your work out there and being unapologetic about it, open source even, and willing to take feedback, will go a long way.

    I am more worried about the many closed source implementations of LLM built products that are being sold and people are depending upon that don't get this great criticism from many different thinking heads.

    1. baxtr · · focus · HN ↗
      Agreed. Anyone can share insights into how to do it better?

      How can we "course correct" with "self-awareness and discipline"?

      1. hmokiguess · · focus · HN ↗
        Self awareness means would be taking a step back and knowing if you're caught in a vicious cycle, trap, loop, pursuing something mindlessly.

        Discipline would be turning this into principles you practice constantly, it's more of a lifestyle rather than a skill you "obtain".

        For example, starting from the position of "I am taking on an idea where I may have knowledge gaps in" you first prompt for research and validation rather than execution. Even if the end result is you were right on your original design. (Sort of a challenge, adversarial, by default)

        It will slow you down, but may lead to more sticky results.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.