3 ms·
I think it's more like confusing people who just want to cook by expecting them to learn hob design and maintenance. The Jobs "bicycle for the mind" line was ab
by TheOtherHobbes 7y ago
I think it's more like confusing people who just want to cook by expecting them to learn hob design and maintenance. The Jobs "bicycle for the mind" line was about the user experience, not the developer experience.
So the fallacy in the argument is that implementation details are relevant to everyone.
They aren't. They're relevant to system builders and people who like tinkering because that is a separate domain to the user domain.
Most users just want an appliance, because a good appliance - like Hypercard, Excel, and maybe VBA - allows them to concentrate on the things that interest them, not on the things that interested the appliance designer when they were building their product.
This is fine for products in the the app store - it's a mark of good design that it reveals exactly as much complexity as it needs to, but no more - but it breaks down when the user domain and the tinkerer domain overlap, as they do in professional software development.
The reason it breaks down is because there is no general solution. No library is ever going to be a perfect snap-in tool that solves your problem for you, no language is going to hide OS-level and library-level abstractions with perfect elegance, and no OS is ever going to have perfectly elegant abstractions for file and network operations, simultaneous and synchronous operations, and so on.
Everyone has opinions about how software should be designed, the problems are essentially open-ended, tinkerers have a tendency to turn everything into an excuse for tinkering instead of a streamlined product/service pipeline, and the result is the mess we have today.
And this is probably how it has to be, given the limitations of human reason.
- nikki93 7y agoI agree for all the 'appliance' stuff; and a lot of times that's what you want. But I think also we should be sure to enable and flood computers with "play" spaces--which are about such 'tinkering' but I think it is much; much more than just tinkering--it's really what enables us to express our humanity IMO. And I think that's actually all types of tinkering; technical or not. And for a lot of 'use' you want to tinker but want the technical part to work; which I agree with. But we still maybe want to keep them open, inviting and friendly somehow. Just some thoughts along this rabbit hole I've been diving into lately--"game studies," "play," etc.-- https://publishup.uni-potsdam.de/frontdoor/index/index/docId/5045 https://publishup.uni-potsdam.de/frontdoor/index/index/docId... collects some references.
- chenglou 7y agoArgh, I promised myself I wouldn't come back to this thread actually; debates around this particular subject I've been part of have been tiresome =) I can assure you that I'm not conflating simple things like user experience vs developer experience. That was the point of the asterisk. I'm also very positive that the creator of Hypercard and Excel do _not_ think of their creation as appliance. The whole point of the discussion around computer and computer languages/systems as tool for thought, is presuming that computing can be another form of mass literacy. Let's also not get into whether this should be the case (and my opinion here is less naive that one might think); I'm just saying that this is the debate. At the risk of exaggerating and drawing an imperfect parallel, the medieval monks also considered human language literacy as a "developer" thing, e.g. "reading the Bible is a separate domain to the everyday life of a consumer". And yes, they did make beautiful books as products/appliances. Again, I'm not saying programming languages will ever be useful to learn for the masses; that's another topic of discussion. I agree very much that there is no general solution, and that tinkerers gotta tinker. Though this is orthogonal to the discussion (FYI I absolutely despise language tinkering/golfing these days; that's why I made sure to talk about this topic without talking about Mu earlier).
- scroot 7y ago> The whole point of the discussion around computer and computer languages/systems as tool for thought, is presuming that computing can be another form of mass literacy. Let's also not get into whether this should be the case (and my opinion here is less naive that one might think); I'm just saying that this is the debate. Exactly right. The Jobs line is a half-baked and perhaps half-understood take on the thinking of people like Kay, Papert, et al. Anyone curious about this line of thinking -- which has fallen way, way out of the popular computing discourse -- might want to check out Andrea diSessa's "Changing Minds" for a decent summary.
- MaxBarraclough 7y agoMandatory link to the relevant Spolsky article, The Law of Leaky Abstractions : https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/ https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a... > the fallacy in the argument is that implementation details are relevant to everyone. > They aren't. They're relevant to system builders and people who like tinkering because that is a separate domain to the user domain. > [...] breaks down when the user domain and the tinkerer domain overlap, as they do in professional software development Agree. The degree to which the two domains cross over, depends on, well, the domain. A driver doesn't have to know much about the workings of a car to pass their test, but as I understand it, pilots do have to have a solid understanding of the workings of their aircraft.
- akkartik 7y ago(Author of OP here.) I don't think computers are like appliances at all. Given the outsized effect that software infrastructure has on our lives, I think computers are more like laws. And my lesson from (a layman's reading of) Ancient Rome and the last 300 years of Western Civilization is that laws are too important to be left to legislators. This is a failure on both sides. We the masses have wanted to treat the hard work of law-making as an externality, and legislators have been happy to take control of them for us because it serves their interest. Both sides think they're pulling one over on the other, and both are being short-sighted. To bring it back to software, it would be great to separate the user experience from the developer experience if we knew how. But we don't currently know how to make a program do precisely what the user intends it to do but not something else like dial home or spam a bunch of people in Vermont or encrypt my hard disk to hold it for ransom. I propose we live in the world we find ourselves in rather than the one we wish we had. This world requires us to invest in understanding computers if we want to use them. > The Jobs "bicycle for the mind" line was about the user experience, not the developer experience. I used the phrase because the conference alluded to it, but I spent a while researching it and would rather not have. You're right that Jobs used it in a blunt, superficial way: https://www.youtube.com/watch?v=rTRzYjoZhIY https://www.youtube.com/watch?v=rTRzYjoZhIY. But he was also using the phrase to refer to technology from Xerox PARC that he did not fully appreciate. I'm glad the term has taken on a life of its own and grown to mean something closer to what PARC intended.