4 ms·

That's actually not a contradiction. As far as I can tell, you can build very complex prototypes. But unless these prototypes can be both trusted and maintaine

by Yoric 2y ago

That's actually not a contradiction. As far as I can tell, you can build very complex prototypes. But unless these prototypes can be both trusted and maintained, that's all they are.

NitpickLawyer 2y ago
> As far as I can tell, you can build very complex prototypes. I think GP was saying you can do more than prototypes. I agree, but it's not (yet) universal on where you can apply it. The best case for my projects has been in trivial but tedious "3rd party integrations". Say you have a mature product but client x wants integration with product z. We are now at a point where we can say "this is our internal model {json dump}, this is the 3rd party integration docs / example {code dump}, write interfaces for this". And it works most times. For things that are a bit more complicated, /architect first and then "now write it" w/ some things from the architect session in context also works. YMMV but don't dismiss it out of habit. Things are moving very fast in this space, and I choose to focus on what works now, not on what doesn't. I'm well aware not everything works, but when it does it saves a lot of time.
- Yoric 2y ago
  We're talking about vibe coding, not just AI-assisted coding. Do you put this in production without review?
  - NitpickLawyer 2y ago
    Oh, my bad, and TIL. I thought vibe coding is the trendy way of saying you're using LLM based code in tools like aider/cline/cursor/windsurf... edit: So I did a quick google, apparently it's this: > Vibe coding is an AI-dependent programming technique where a person describes a problem in a few sentences as a prompt to a large language model (LLM) tuned for coding. The LLM generates software, shifting the programmer’s role from manual coding to guiding, testing, and refining the AI-generated source code.[1][2][3] Vibe coding is claimed by its advocates to allow even amateur programmers to produce software without the extensive training and skills previously required for software engineering.[4] The term was introduced by Andrej Karpathy in February 2025[5][2][4][1] and listed in the Merriam-Webster Dictionary the following month as a "slang & trending" noun.[6] (from wiki) So ... now I'm confused again. I don't see the no testing / reviewing part in here. Is vibe coding the new AGI, where everyone has a different definition?
    - Yoric 2y ago
      Well, when Karpathy introduced it, I seem to recall he claimed that he didn't look at the code, just put it in production. But it's entirely possible that there may be several definitions around by now.

by Yoric 2y ago

That's actually not a contradiction. As far as I can tell, you can build very complex prototypes. But unless these prototypes can be both trusted and maintained, that's all they are.

NitpickLawyer 2y ago

> As far as I can tell, you can build very complex prototypes. I think GP was saying you can do more than prototypes. I agree, but it's not (yet) universal on where you can apply it. The best case for my projects has been in trivial but tedious "3rd party integrations". Say you have a mature product but client x wants integration with product z. We are now at a point where we can say "this is our internal model {json dump}, this is the 3rd party integration docs / example {code dump}, write interfaces for this". And it works most times. For things that are a bit more complicated, /architect first and then "now write it" w/ some things from the architect session in context also works. YMMV but don't dismiss it out of habit. Things are moving very fast in this space, and I choose to focus on what works now, not on what doesn't. I'm well aware not everything works, but when it does it saves a lot of time.

Yoric 2y ago
We're talking about vibe coding, not just AI-assisted coding. Do you put this in production without review?
- NitpickLawyer 2y ago
  Oh, my bad, and TIL. I thought vibe coding is the trendy way of saying you're using LLM based code in tools like aider/cline/cursor/windsurf... edit: So I did a quick google, apparently it's this: > Vibe coding is an AI-dependent programming technique where a person describes a problem in a few sentences as a prompt to a large language model (LLM) tuned for coding. The LLM generates software, shifting the programmer’s role from manual coding to guiding, testing, and refining the AI-generated source code.[1][2][3] Vibe coding is claimed by its advocates to allow even amateur programmers to produce software without the extensive training and skills previously required for software engineering.[4] The term was introduced by Andrej Karpathy in February 2025[5][2][4][1] and listed in the Merriam-Webster Dictionary the following month as a "slang & trending" noun.[6] (from wiki) So ... now I'm confused again. I don't see the no testing / reviewing part in here. Is vibe coding the new AGI, where everyone has a different definition?
  - Yoric 2y ago
    Well, when Karpathy introduced it, I seem to recall he claimed that he didn't look at the code, just put it in production. But it's entirely possible that there may be several definitions around by now.