[–] 0 points 1 month ago* (5 children)

There’s not really any such thing as a one off web page.

Of course there is. What an absurd thing to say. A very obvious example is event websites, e.g. for weddings.

I’m calling bullshit on that

Maybe it depends on the language but I've recently vibe coded two tools in Rust and I've skimmed the code and it's perfectly good Rust. I would accept it in a PR - even if I was being as picky as I'd really like to be in reviews. I don't think that would have been the case 3 months ago though.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (7 children)

    People think that once they have something on the screen that looks finished, the project is finished.

    For .one-off web page that is true. You and I might not like that under the hood it's a mess but we have to accept that if it works anyway and nobody is going to need to change it, that's fine.

    Also the latest models don't even make a mess any more.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago

    Git has a mutable map whose keys are strings, and whose values are content-addressed objects. The keys are conventionally formatted as file system paths

    I used to think this too, but I think it's more accurate to say the keys are filesystem paths. Try creating branches foo and foo/bar. That would be fine if the keys were strings. I vaguely recall there was some effort to make that actually work, but it doesn't today.

    Do you understand why is it origin master in one command, and origin/master in the other? I didn’t, until a few weeks ago!

    I mean I understood that it was because Git has a terrible CLI, and... that is ultimately still the reason. There's no fundamental reason it couldn't have been consistent. It just isn't.

  • source
  • [–] 4 points 1 month ago

    Except that the job was never to type code, it was to deliver valuable software. People who can still do that can still get paid by organisations that need that to be done.

    Yeah but probably not nearly as much.

    You still need to know how to code to vibe code effectively today, but at the rate things are improving I wouldn't bet on that still being true in a year.

    Programmers have had insane salaries compared to the average white collar jobs for decades. That might end. 😭

  • source
  • [–] 1 point 1 month ago (9 children)

    I think the effect you're seeing is that different people have different levels of "good enough", and also they work in different domains where AI became good enough at different times. E.g. for one-off web page design it's been good enough for a long time.

    I never said this for earlier models, because they did suck for things like Rust and SystemVerilog. Now they don't.

    I'd share some things I've vibe coded that work basically perfectly but they're linked to me real name, but you could have a look at the Mold linker which was recently vibe-ported to Rust.

  • source
  • parent
  • context
  • [–] -1 points 1 month ago

    The days of constant hallucinations are over.

    I get it - I was pretty much where you are a six months ago. AI just produces low quality slop. You have to watch it like a hawk because it will just bullshit some plausible but totally wrong solution. It will write tests that don't test anything, go round in circles making nonsense changes trying to fix things that are fundamentally wrong.

    Yeah, those days are gone. The latest models (at least Astra 6 or Opus 5.5) are actually competent.

    I have no skin in the game in convincing you but you're pretty much in the "the iPhone is only popular because of Apple fanboys" stage of denial. I guess the only real cost for you is wasted time and being late to the party, but... that's probably still bad.

    And no I'm not super happy about this. I mean it's great that I can now easily vibe code the tools I always wanted - and the vibe coding actually works, unlike 6 months ago.

    But it also doesn't bode well for me having a job and I like having a job. 😔

    But I'm not going to stick my head in the sand and pretend that AI is still shit just because it would be great for me if that were the case.

  • source
  • parent
  • context
  • [–] 3 points 1 month ago

    There's a lot of people here that clearly haven't ever tried what you're describing op (or maybe tried recent AI at all).

    I have. I think it's a totally valid question. Sometimes when I'm getting AI to do stuff it reads the docs and then tries stuff anyway and finds the docs are wrong.

    I also often use AI to generate docs for undocumented things.

    But I think it does still make sense to have docs for a few reasons:

    1. They show the intent explicitly, rather than having it inferred. Same reason anything explicit is better than implicit, e.g. static types.
    2. It spends fewer tokens to read docs than to constantly reverse engineer software.
    3. It's also quicker.
    4. Sometimes you do still want to understand the thing...
  • source
  • view more: ‹ prev next ›