3 ms·
I don't think aiming at the results/effort equation is a bad heuristic for lots of things, depending on how effort is defined. Though maybe it isn't a good equa
by _delirium 16y ago
I don't think aiming at the results/effort equation is a bad heuristic for lots of things, depending on how effort is defined. Though maybe it isn't a good equation for schooling in particular, and I agree defining people as unintelligent based on them putting in effort isn't a good strategy.
It's the basic heuristic of elegant code, for example: elegant code maximizes the ratio of results to coding effort. The opposite is when you get the results, but by slogging through a bunch of inelegant boilerplate.
It's also the whole premise behind the "hacking the workweek" type ideas, though I realize not everyone likes those.
If anything, I'd say it's a pretty pervasive part of hacker culture, and what differentiates it to some extent from "normal" engineering culture: hackers aim for that results/effort win, the cool hack, virtuosic performance, etc., rather than the N-hour straightforward, carefully managed slog. Not even just because it saves time/money, but because somehow it's intrinsically interesting to see people finding ways to get great results via a route other than "I just plowed through it and got it done". That's sometimes necessary too, but it's not the part that gives the hacker spirit a spark.