3 ms·
I think the article might've started with something like: The current practice of software development has a lot of duct-taping together of off-the-shelf compon
by neilv 4y ago
I think the article might've started with something like: The current practice of software development has a lot of duct-taping together of off-the-shelf components by people who don't sufficiently understand what it's doing.
There certainly are important points to be made there, and the article makes some of them.
I didn't understand all the terminology choices and definitions. For example, where does Papert's theory of Constructionism fit into this dichotomy of "preliminary learning" vs. "on-demand learning"?
- hinkley 4y agoI learned a lot of low level things starting out. As the abstractions piled on it became clearer and clearer that I had mechanical sympathy that other people did not, but the world changes underneath you, especially when it's all abstracted away anyway (how would you know if the foundations have been swapped out underneath you?). I got a refresher course about ten years ago working on embedded software, and I'm overdue for a booster. I'm kind of hoping that IoT or open source firmware for SOCs and BMCs will give people some more fodder for learning systems thinking concepts that are currently being buried behind giant frameworks and stackoverflow.