Giles Bowkett summons monsters
raganwald.posterous.com
raganwald.posterous.com
Those details are often things that are a matter of preference. There are good and bad arguments for both sides, and most of those arguments have been made many, many times already. Different people will hear the same exact arguments, draw on their own experiences and values, and come to different conclusions. And that's okay.
Which isn't to say that details are always irrelevant: just that you're missing a lot when you focus on the details to the exclusion of the larger point. Like in this post: it doesn't really matter whether or not Giles is baiting people intentionally. It may be true, it may be false, but it's not the point. The point is that people are responding as if he's doing it anyway.
My favorite example are analogies. Every single time one is made, it results in a string of other comments attempting to correct it or improve it. "It's like driving a car down the freeway without any wheels"... "No, it's really more like driving a tractor trailer on a country road without wheels and a windshield". Every. Single. Time. And I'm as guilty of this as anyone.
It often makes for frustrating reading, especially when you're already familiar with the argument and aware of the most common mental traps, but have to read them over and over again trying to get to the good stuff.
Hey, this idea is my Intellectual Property! I invented it to keep the morons at bay during Usenet's Eternal September, beginning with AOL, Prodigy and CompuServe's addition to Usenet in 1993. I always tried to put "lightning rod" prose into any Usenet article to divert the idiots into responding with idiocy. Only people with some knowledge can pass up a "lightning rod" and deal with the real issues.
However, although I think Raganwald is basically onto something, it's not entirely deliberate. It never occurred to me that after complaining how Bundler breaks convention over configuration, people would tell me that configuration options are the solution to "bundle exec foo."
This is the kind of thing Reg might refer to as a trap, but there's a simple general principle that generates traps. Trace your idea from a specific to a principle and watch how few people can follow you there.
Also, I've actually blogged that Alan Kay quote many times, and I try to hammer the point whenever I have a chance, because I think it's one of those overlooked bits of genius that really helps anyone who gives it the thought it deserves. For instance: anything which is driven by fashion is going to go in cycles. What does that mean?
Clothing of course is driven by fashion. Lots of fashion designers raid thrift shops to get new ideas from old clothes. Fashion drives music. Bands re-record new versions of old songs all the time, dance music constantly samples and recycles itself, rappers sample old grooves and bring them back to new life and put them in front of new audiences. So maybe if you work in an industry driven by fashion, a pop culture, you'll want to dig into the past and find "new" ideas to steal. Like the revolutionary idea that GUIs should use MVC, for example. The big "new" idea in client-side JavaScript is literally the oldest idea there is when it comes to UI.
I mentioned this in another thread, connected to my actual rant, but I'll say it here again: I predicted JS MVC (eg Backbone) in 2005 or 2006, and built my own crappy version in 2007 or 2008. It's not magic future genius powers. When you know it's fashion, and you know fashion is cyclical, you can just watch the wheel turning.
But I don't think the Alan Kay thing is the only thing in there worth thinking about. I basically put in stuff for arguers to argue about and stuff for thinkers to think about. Some people love arguing and hate thinking! That's not my style, but I don't mind if they have fun too.
Yeah, I see how saying he “used to” makes it sound like he’s dead or had total personality replacement surgery. I’ve changed that, thanks.
Or were high-ceremony Java enterprise folk doing tdd all along and rails just adopted it? I don't know but I suspect they were at best pretending to
IMO though, Rails moved this from "something done by advanced programmers" to "something done most of the time".
The most brilliant contribution for me was: the migrations.