In much the same way that buying produce makes you a great farmer.

Farming is a funny example to use, given that it's one of the best examples of an industry that's continually revolutionized by evolving technology. Farming today is about owning the best tractor.

▲

theshrike79 4 days ago | parent | prev | next [-]

It's the difference between lovingly crafting heirloom tomatoes in small batches vs producing a consistent multi-ton quantity of tomatoes at an industrial scale.

There are uses for both, but job/compensation wise the heirloom grower isn't in the majority.

▲

metalcrow 4 days ago | parent | prev [-]

no, it makes you a great chef

▲

worthless-trash 4 days ago | parent [-]

I believe you reinforced the point.

▲

aroman 4 days ago | parent [-]

I think you missed the point.

produce : chef :: code : programmer

chefs use produce to create dishes of food; chefs do not generally grow their own food. the point they were making is that the code is actually the means to the end, not the end in itself. to wit: i do not write assembly.

▲

acjohnson55 4 days ago | parent | next [-]

This may be more correct than you know. Chefs actually don't cook food customers eat. They plan the menu and manage the operations. The cooks cook.

	▲	theshrike79 4 days ago \| parent [-]
		They know how to cook and can if needed, but usually don't bother as they have 15 other restaurants to manage.

▲

worthless-trash 4 days ago | parent | prev [-]

No, I understand the point, it means that people drawing the analogies don't understand the original intent was production, not consumption.