I think that the training wheels example is wrong. A quick search suggests they hinder learning how to ride a bike. Anyway, I have a few more examples ([actual skill] / [scaffolding skill]):
re 2: Now that you mention it, I realized sharpening can be easily outsourced. My mistake.
re 1: I don’t see it, buying pre-chopped onions is simply not equivalent to having a freshly chopped onion and some vegetables cannot be bought pre-cut. While cutting isn’t a bottleneck for most people I had this chain in mind: (no cutting skills) → (cooking takes more time and is less pleasant) → (Less willingness to try new or complex recipes).
(Also, if you don’t have proper technique, you’re at a higher risk of cutting yourself. In that respect, it’s like free climbing / using safety ropes)
re 3: I had self-experiments in general in mind (people run self-experiments, without knowing statistics, or even gathering data), but it did not occur to me that not all self-experiments are QS (probably most aren’t). As written you are, of course, correct.
Most of your examples seem more like “prerequisites” or basic skills that you build on. But scaffolding is a thing you build up to get something else done, then get rid of afterwards. So, a scaffolding skill would be a skill that enables you to learn how to do something you actually want to learn, but once you have learned how to do that thing, you no longer need the scaffolding skill.
Algebraic notation can still be useful to a chess player. Knowing basics like how to properly cut things is integral to cooking. Debugging is an essential skill for programming. Etc.
A couple better examples of scaffolding skills:
In calculus, learning to calculate a derivative using limits. Once you have the concept of derivatives down, you wouldn’t go through that exercise, you would use the the various formulas (or a math program) to actually calculate them.
When trying to get a business group to adopt Agile methodology, using strict Agile Scrum, which gives a bunch of prescriptive processes, and demonstrate how to “do Agile”. But, teams that have internalized the Agile philosophy tend to ditch many of those processes (or at least strict adherence to them) as they move toward more efficient approaches, tailored to their situation.
I think that the training wheels example is wrong. A quick search suggests they hinder learning how to ride a bike.
Anyway, I have a few more examples ([actual skill] / [scaffolding skill]):
Playing chess well / reading algebraic notation
Writing blog posts / touch typing
Cooking / cutting vegetables (also other things)
Cutting vegetables / sharpening knivesQSself-experiments / knowing statisticsProgramming / debugging
Parkour / running
Dancing / aerobic endurance (This might be stretching the concept a bit)
Training wheels have been replaced with balance bikes for this reason.
Disagree with
Cooking / cutting vegetables (also other things)
Cutting vegetables / sharpening knives
QS experiments / knowing statistics
The first two is pretty much like sketch / making pencils and paper, and the third one is absolutely essential and not a skill than you can not have
re 2: Now that you mention it, I realized sharpening can be easily outsourced. My mistake.
re 1: I don’t see it, buying pre-chopped onions is simply not equivalent to having a freshly chopped onion and some vegetables cannot be bought pre-cut. While cutting isn’t a bottleneck for most people I had this chain in mind: (no cutting skills) → (cooking takes more time and is less pleasant) → (Less willingness to try new or complex recipes).
(Also, if you don’t have proper technique, you’re at a higher risk of cutting yourself. In that respect, it’s like free climbing / using safety ropes)
re 3: I had self-experiments in general in mind (people run self-experiments, without knowing statistics, or even gathering data), but it did not occur to me that not all self-experiments are QS (probably most aren’t). As written you are, of course, correct.
Most of your examples seem more like “prerequisites” or basic skills that you build on. But scaffolding is a thing you build up to get something else done, then get rid of afterwards. So, a scaffolding skill would be a skill that enables you to learn how to do something you actually want to learn, but once you have learned how to do that thing, you no longer need the scaffolding skill.
Algebraic notation can still be useful to a chess player. Knowing basics like how to properly cut things is integral to cooking. Debugging is an essential skill for programming. Etc.
A couple better examples of scaffolding skills:
In calculus, learning to calculate a derivative using limits. Once you have the concept of derivatives down, you wouldn’t go through that exercise, you would use the the various formulas (or a math program) to actually calculate them.
When trying to get a business group to adopt Agile methodology, using strict Agile Scrum, which gives a bunch of prescriptive processes, and demonstrate how to “do Agile”. But, teams that have internalized the Agile philosophy tend to ditch many of those processes (or at least strict adherence to them) as they move toward more efficient approaches, tailored to their situation.
I have, indeed, misunderstood the concept—will retract my comment.