Re:GPT-5.6
by desterothx on Friday July 10, 2026 @10:00AM
(#48860055)
Really almost all benchmarks I look at have a cost per task column, which is basically the code size metric if you take an extra step
[ Parent
| on HN ]
Not at all. The model could (and sometimes should) burn all the money it wants, and then produce a single line of actual production code. Only some things, e.g. full rewrites, have clear cost - LoC scaling.
For my usage, I would very much prefer if those $/task were being spent in thinking and experimenting, and the actual output would be as short and maintainable as possible. “maintainability” is a vague target of course, but it’s at least somewhat correlated with code size.
Re:GPT-5.6
by nathanasmith on Saturday July 11, 2026 @08:01AM
(#48871288)
Exactly. To butcher a cliche, if the model has 6 hours to chop down a tree I want it to sharpen the axe for 5 hours.