Aaron Swartz: Sweating the Small Stuff

  • Jottit may end up being the classic example of why striving for perfect code is a bad idea.

    Half a year on a textarea... I hope it turns out to be awesome.

  • This post seems like a pretty transparent attempt to justify his procrastination. It's a really easy trap to fall into. Actually releasing to the public is like selecting the "Hurt Me Plenty" option in Doom, it's not an easy thing to do.

    My partner and I took turns emailing this quote to each other as a reminder to keep ourselves intellectually honest:

    "Perhaps the most important reason to release early, though, is that it makes you work harder. When you're working on something that isn't released, problems are intriguing. In something that's out there, problems are alarming. There is a lot more urgency once you release. And I think that's precisely why people put it off. They know they'll have to work a lot harder once they do." -- Hardest Lessons #1

  • On one hand I think there are kudos to give for bucking the irrationally extreme "release early, release often" trends that seems to abound. I've seen a lot of bad software released under this banner.

    On the other hand, that's an awful long time for the features I see in a really crowded market.

  • There's a guy posing as PG in the comments. It's pretty malicious too, because when you click on "PG" it sends you to a web archive of Paul's Infogami blog.

    I'm amazed at how much time people devote to making other people look bad.

  • That looks alot like the idea behind my site scrapages. Although I built that in about 2 weeks.

  • Talking up the complexity just doesn't cut it for me with this. It's a simple little thing. No way are there "500 different things to do". Maybe 500 lines of code :)

  • How did you manage to post the reddit redirect link? I wonder if reddit still logs it as a click through when they are not the referrer.

  • undefined