• 2 Posts
  • 18 Comments
Joined 3 months ago
cake
Cake day: August 10th, 2026

help-circle









  • The code I get from coding agents is better than code I can write myself. It’s better than most of the code I’ve seen from collaborators over the course of my career. I think it takes skill to get those results out of a coding agent,

    So if you are weaker at programming than an LLM, why do you think you are better at prompting LLMs? There are skills required in either case, and from what I’ve read, it seems it requires just as much attention to detail to keep the LLM from going “off-script” and time that used to be spent getting code past the compiler (or unit tests) is now spent getting code past the LLM.

    I can produce thousands of lines of good, tested, understood code in a day

    Well, “good” and “understood” are doing some heavy lifting there. From what I’ve read, the moves made by AlphaZero (Google’s AI Go playing engine) are upsetting to Go masters because the moves are rarely understood by them. While AlphaZero plays by the rules, the “output” (so to speak) is so alien that it might as well be random moves that just happen to win. It’s hard to determine if the moves are good if the reasoning behind them are not understood.

    On your coding thousands of lines of code, over the past forty years we’ve slowly hammered into upper management that “lines of code” is not a good metric, and now that’s suddenly tossed out the window and “more more more” is the mantra of the day? I thought “no code” was the best code.

    Without a coding agent I tap out at a few hundred lines per day.

    The last year at my previous job, I wrote less than 100 lines of code, and it wasn’t because I’m a slow typist. It wasn’t even because I wrote 10,000 lines then deleted 9,900 of them. No, it was the constant meetings that slowed the pace down for everybody!


    score 1 · canonical


  • UB has nothing to do with supporting different hardware behaviour.

    I thought some of UB was to deal with different CPU behavior. Some CPUs trap on signed overflow; others wrap. Some can do both, either by setting a flag (VAX) or instruction selection (MIPS). Some CPUs, when executing 1 << 100 do 100 rotates; other mask to the bit width of the type (8086 would do all rotates, 80286 started masking).

    the compiler encounters some code, and assumes that UB does not happen

    I hate that compilers assume that. I know that programmers don’t intentionally want to invoke UB in C, but there are so damn many footguns in C that I seriously doubt any non-trivial C program is completely UB free. And if a compiler can delete NULL checks in certain circumstance (<cough> <cough> GCC <cough>) that it at least should warn about it deleting a NULL check written by a programmer, but I’ve been told that such checks are beyond the ken of compiler writers for some obscure reason.


    score 1 · canonical