Live data from Hacker News

Good Software Takes Ten Years. Get Used To it.

joelonsoftware.com

1–10 of 29 posts

Re: Good Software Takes Ten Years. Get Used To it.

#3
post #2

7-year old article, although that doesn't invalidate it. I think what does is that web development (particularly using frameworks) is much more tractable and probably more lightweight than creating an office suite or operating system.

Yeah, I noticed the 2001 dateline, too... it was especially apparent when he said (paraphrasing) "Mozilla - when is that thing getting released, anyway??" :)

I thought it was surprisingly relevant today; especially because it was written during the sobering post-dot-com rush. A lot of those lessons need to be remembered. You're right that a lot of his points are more related to consumer software, but he does have a few gems in there about web development, too, like his points about "Overhype syndrome" and the myth of "Internet Time."

Re: Good Software Takes Ten Years. Get Used To it.

#5
post #2

7-year old article, although that doesn't invalidate it. I think what does is that web development (particularly using frameworks) is much more tractable and probably more lightweight than creating an office suite or operating system.

I don't have any experience with Fog Creek products but their software should be 70-80% good by now if what he says is true.

Re: Good Software Takes Ten Years. Get Used To it.

#6
post #5
post #2

7-year old article, although that doesn't invalidate it. I think what does is that web development (particularly using frameworks) is much more tractable and probably more lightweight than creating an office suite or operating system.

I don't have any experience with Fog Creek products but their software should be 70-80% good by now if what he says is true.

It is 70-80% good. (FogBugz)

Re: Good Software Takes Ten Years. Get Used To it.

#10
The message that I took away from this article was that good software has to deal with the likely exceptions it will run into in the real world, using real world data.

When I built the first version of the Ambient Clock (http://ambientclock.com), I groveled through the vagaries of iCal implementations. It was a nightmare.

I breathed a sigh of relief when we decided to use GData: a nice, clean API. But what bit me next was the USER data that was in there. Weirdly formatted, strange timezones, oddball recurrences and other stuff. The nice, clean API can only hide you from so much.

My point is that it is hard to write software that deals with human-generated content, in some structured way. As soon as you hit actual people, you can assume that they'll do things differently than expected: using semicolons rather than commas to break up bands, using a different DATE format when specifying things...

I believe Joel's definition of 'good software' is software that has learned to deal. And so can be used in a vast number of situations, by a vast number of people.

Post reply on HN