How I Explained REST to My Wife
tomayko.com
tomayko.com
Ryan: The web?
Wife: Yeah.
Ryan: Hmm. Well, it’s all pretty amazing really. And the funny thing is that it’s all very undervalued. The protocol I was talking about, HTTP, it’s capable of all sorts of neat stuff that people ignore for some reason.
Wife: You mean http like the beginning of what I type into the browser?
Ryan: Yeah. That first part tells the browser what protocol to use. That stuff you type in there is one of the most important breakthroughs in the history of computing.
Ryan went down a completely different path than I would have. I don't think most people who ask how the web works care about the http protocol. At least I wouldn't, if I didn't know better. I think I'd be more interested in how the network infrastructure is laid out and how requests get from my computer to a server and the data back and rendered. http is really just an implementation detail (people did this far before http existed).
To describe the Internet when someone asks how the web works would be like describing how the iOS works when someone is curious about a specific app.
HTTP and HTML, while both are fundamental to the web, are also just implementation details. HTTP has evolved a fair bit since its inception for the web (there was no PUT or POST, for example).
To take your analogy, it would be like describing Cocoa library when your wife asks how an app works.
"Sounds like GET is a pretty important verb."
Even though it's quite vague, even I learn one or two things, quite an interesting read! Something to share on Tweetbook I guess.
"In parallel with the software engineering research in architectural styles, the object-oriented programming community has been exploring the use of design patterns and pattern languages to describe recurring abstractions in object-based software development. A design pattern is defined as an important and recurring system construct. A pattern language is a system of patterns organized in a structure that guides the patterns' application [70]. Both concepts are based on the writings of Alexander et al. [3, 4] with regard to building architecture."
That's so much simpler than "We need to be able to talk to all machines about all the stuff that’s on all the other machines. So we need some way of having one machine tell another machine about a resource that might be on yet another machine."
Your wife may have understood it, but Ryan's wife lacked the CS background.
If you want the hard numbers check the number of ungraduates/graduates in CS/IT, for males and females.
I'm saying that women are not capable of grasping IT (hell, the very first programmer was a woman, mrs. Lovelace). I'm saying that in actual, real life, they statistically don't want/care/attempt to.
Maybe they are just smarter and go where the big money are these days (biology), as well as the better hours.
You're right in one aspect: of the very, very few people in the world who know about computer science, most (more than half, anyway) of them are men.
If it was his dad instead, would there be any issue? https://gist.github.com/1525252
I mean, my wife is smarter than me and has a doctorate and a lot of letters after her name, but she's never cared to learn too much about how the drivetrain in a car works. If she asked a simple question like "How does a car's transmission work?", I highly doubt she'd be happy if I just linked her some pdf's covering the physics and mechanical engineering of CVT's and said, "you're welcome!"