• 0 Posts
  • 152 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle


  • I think people assume the AI code goes first, but it’s not really like that.

    I just busted out a half day of coding. Really impressive stuff for my standard and was just in flow with little optimisation breakthroughs popping in my head as I made it through. Output looks great, all working as expected, documented and commented my new things in case I forget them later or want to explain them to the team.

    But later, I’ll probably run it through a model real quick and expect at least one change, usually around tidying things up or an opportunity to optimise a block here or there a bit more. Basically tighten up any loose screws or be pointed to big obvious things I somehow missed.

    Really, I think that’s how most devs are making use of it. It can be frightening the shit LLMs come up with starting for scratch (that goes with anything), or even 60-70%. Doesn’t matter how good the prompts are, at the end of the day, it’s relying on Frankencode sourced from all over the place to apply solutions. It has no consistent and familiar, style, logic, or “accent” in its language. But if it’s got an established and detailed base, concept, and direction (such as a mostly completed chunk of code), frequently enough it’ll assist well with finding dumb shit.

    It’s like a final phase thing, to get you beyond, “It seems work work well; good enough.” to “It’s definitely working well. This is done for now.”

    I like to think that’s what’s going on here because anyone with even moderate developing knowledge/skill/experience totally sees just how bad LLMs are at coding.



  • I’ve always subscribed to the idea that Lucifer was the good guy that tried to overthrow God but lost. He got A THIRD of the angels backing him. That’s not insignificant. Shit was going on and people were unhappy.

    Even though the Bible is written by the victor, it somehow still manages to show how fucking evil God is.

    The Abrahamic religions and their followers are completely nuts or simply just don’t know much about their faith.



  • “It’s a simple question for any enterprise. Would you like something that’s 10 percent of the cost if it’s 90 percent as good as the best, or do you want to pay that 10 times higher cost?”

    That really depends…

    90% is disasterous. It may sound good because it’s “just” 10% off 100%, but it’s awful. Two iterations reduces that to ~0.01%< but that’s still pretty bad. Obviously the more complex, the higher the risk and the more demand and time per iteration. The machine also has no concept of criticality, so how much is being saved with three or even four iterations to assure failure is basically zero?

    “Then the question is: how many tasks require that? I would tell you some do, but the vast majority, summarizing an email, examining a contract, answering a customer call, composing an email, all of those can be done as well with the much cheaper answer.”

    Imagine 10,000 emails an hour through your enterprise and 1,000 times It fucks up. Anything from missing info to misinterpreting to just straight up modifying/deleting. No concept of criticality per email. 8,000 in a 9–5 office. 24,000 a day for a global enterprise. That’s what 90% looks like.

    Then you got “examining contracts” and all the other stuff he mentioned…






  • I’ve had Claude Code for a while now.

    Figured it out.

    You do all the work, then as climax is starting, but you’re exhausted, you bro tag it in and cuck. It’s got this.

    Then one of two things happens:

    1. Climax. No great. Standard, really. As expected. But you got a drink of water in that time, the job’s done. It’s hard to fuck up at that point. You just let it know what it should’ve done instead. But it’s okay, first time for everyone. Just ignore the fact you’re making yourself redundant. All good.
    2. Spend more time halting things, explaining how to do the deed, as you and the project make eye contact expressing how deeply unsatisfied everyone is.Just ignore the fact you’re making yourself redundant. All good.

    So. If you want to use an LLM as a primary coder, do 80% of it yourself and expect these two outcomes.

    Otherwise, sit in the corner and explain to your project lead that many screams happened but the safeword was between Claude and the project, so how could you know when it went too far? You burned tokens as requested.

    Claude will remain employed but you will not, obviously. Unless you ignore this advice entirely and old school it, in which case Claude will remain employed but you will not BUT you’ll be reemployed to go through everything above again.

    Edit: Honestly, if you want a code assistant—I get it, the annoying things of coding are no longer annoying—go local.





  • abandoned because its unmaintainable

    Exactly this. It’s hard enough maintaining my own code. It can take a good 15 mins or so to familiarise myself with something I haven’t worked on in a short while. Seeing code that isn’t mine is very challenging. Not the code itself, but the methods and structures used by the other person. All that has to be done before hunting bugs and adjusting features. Then of course there’s the things you don’t know about that can be easily missed.

    An AI would need to thoroughly know the code and detailed context on the decisions behind it all, every session, in order to be able to maintain it with vibe, because the vibe coder won’t know any of this.