• cinoreus@lemmy.world
    0·
    5 hours ago

    A friend of mine once called it brainrot engineering, but I gotta admit cuck coding is better.

  • Vetis@sh.itjust.works
    0·
    7 hours ago

    That’s it, I’m calling it like that now. Using Microslop’s CopePilot to do some cuck coding.

  • Edges@lemmy.zip
    0·
    8 hours ago

    Oh god Claude is coding it so well, I never could have written satisfying code like that. Oh man its making a bit of a mess though…I better get in there and clean up

    • saltesc@lemmy.world
      0·
      6 hours ago

      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, the annoying thungs of coding are no longer annoying—go local.