You know, I just can't stand it when people get all pompous about a subject for which they obviously know nothing -- besides their armchair philosophy about how the world
should work.
Go get a degree in pedagogy and then come back and .... Oh wait, you won't because then you'll know how idiotic your arguments are.
As if you weren't playing semantics to begin with. Pick a meaning and stick with it. Either you are talking about code reuse (for a three line function!) or you are talking about
prior knowledge review. They are separate concepts.
[For] instance, using `min_element' in `selection_sort()' |
Unfortunately for that example, an unoptimized selection sort doesn't need to do more than one thing as it loops through the I unsorted set. OP's problem does. (Optimized versions do:
http://www.cplusplus.com/faq/sequences/sequencing/sort-algorithms/selection-sort/#optimization)
They should be able to see it in these kind of toy problems. |
toy problems are for instructional purposes... Precision to large project guidelines on beginner-level homework is overload, both for the student and for the lesson objectives.
On a fifty-line toy homework problem??? LOL!
Another beautiful example |
Ah, yes, because if you think that is a valid counter-example then I am obviously wasting my time with you. Doing
one thing nicely is pretty and all... But it still says nothing against doing
multiple things nicely.
JSYK, I only bother debunking the drivel here in OP's otherwise untarnished topic so that others can begin to recognize it.