4 ms·
Cooking may not be the best analogy. What if everyone started learning to build bridges instead? Sure, the general population might benefit from knowing how bri
by derekerdmann 14y ago
Cooking may not be the best analogy. What if everyone started learning to build bridges instead? Sure, the general population might benefit from knowing how bridges work and what loads they can take, but when a bunch of inexperienced, improperly educated bridge-builders start trying to create new ones because it pays well, we end up with dangerous bridges.
Jeff's article is trying to point out that while understanding code isn't a bad thing, coding isn't the most important part of writing software. Those who think it is end up writing code without purpose, something I consider as dangerous in the long term as shoddy bridges.
- icebraining 14y agoShoddy bridges aren't bad, relying on them is. The fact that Bloomberg will write some code doesn't mean we'll have to use it, just like I have plenty of code in my HD that I don't throw into the world, because it's absolute crap. If we could all build bridges in the our own yard, I think we'd see some of new fantastic bridges which we could re-use. With coding, we can.
- telent 14y agoBuilding bridges may not be the best analogy. What if everyone started learning to dance the macarena instead? Seriously, cooking as an analogy highlights a difference between private recreational practice and public for-pay professional practice. Building bridges, unless you live in a place where everyone has a backyard with a river in it, not so much.
- jkahn 14y agoI don't think anyone is saying that everyone should write professional software. Just that it would be beneficial if they learned the equivalent of making a ramp for a wheelbarrow in the back yard.