[StarlaAtNight]

These online tech spaces always assume that saving on compute, storage, and memory are the ultimate targets for optimization.

I’ve worked (mostly on business/data teams) in companies for 10 years, and have to say, saving on technical debt and human inefficiency w/ a codebase typically far outweighs the computational metrics

How might we incorporate that in a metric-like way?

[lysecret]

I agree. However simple to understand code with high human efficiency is nearly impossible to measure. Honestly, maybe ChatGPT could give you the best evaluation/measure of that.

[Shish2k]

“write code clear enough that an LLM can look at it and create an accurate summary of the high-level goals” gives me similar vibes to “explain like I’m 5”, which seems like it could be an interesting metric (and my gut tells me that things will go horribly wrong as soon as somebody turns this metric into a target :D)

[marcosdumay]

It looks like a metric of the kind of lines of code.

Hugely useful for measuring a lot of things. But obviously bad for optimizing even if it's not a formal target.

[adammarples]

It's easy to measure. You sit a dev down in front of it and time how long it takes them to understand it. That's not just an estimate that's the key value itself.

[karles]

Well, human processes can be visulised and their completion time can be estimated, as can possible breakdowns.

Eliminating breakdowns thus eliminate "waste" in required effort, coordination etc.

So I don't see how human processes differs from technical ones that much...