News for hackers. Stuff that matters.
Re:"Do it right" is more important than "Release Early" by davidw on Thursday June 21, 2007 @08:31AM (#29798)
Obviously it depends on what you're up to, but I think that in terms of startups, I'm much more inclined to trust PG's judgement than this guy's. In the article, he cites "40,000 lines of code" as something that was impressive to PG in an interview, and then bemoans the fact that they may have to "throw out and rewrite most of their code". I wonder if that's the same 40,000 of Zenter code that Google might have to rewrite in any case to make use of Google's infrastructure?

He also complains about reddit, but once again - they certainly "made something people wanted" even if it does/did have its share of bugs (clear text passwords...).

This is one of those things that needs to be balanced. You do have to have something that basically works, and doesn't crash all over the place, but sometimes adding new features or doing other things might be more important than making everything 100% bulletproof.

Re:"Do it right" is more important than "Release Early" by mm on Thursday June 21, 2007 @08:56AM (#29800)
rewriting code isn't as bad as some would claim. Because the logic of the code has already been set, a rewrite of the app in another language should take no more than 2 weeks. This is esp. true if your app uses an MVC framework where the view template is separated from the logic.
Re:"Do it right" is more important than "Release Early" by shiro on Thursday June 21, 2007 @03:32PM (#29886)
If you can replace the whole system, yes. It's most of the case for early statups where you have only a few developers communicating intimately.

When you write components used by multiple groups, things get far more complicated; you have to provide some stubs so that other party's old code keeps working until they finish migration. Here, at least doing protocol right is essential. (Web app has advantage here, since you can just ride on existing protocols.)