News for hackers. Stuff that matters.
Re:PuTTY 0.61 released by cbs on Wednesday July 13, 2011 @11:02AM (#2759159)
Putty is a great case to look at next time you hear someone trumpet the benefits of how fast or often their code is deployed to users.

Everyone knows the waterfall model is a bad idea, what I wonder is how fast of iteration is too fast? What does the tacit assumptions of multiple releases a day being a good thing say about a product? Does the browser thin-client target enable development process anti-patterns?

Re:PuTTY 0.61 released by beaumartinez on Wednesday July 13, 2011 @11:35AM (#2759276)
Fast iteration has nothing to do with adding superfluous features.

PuTTY was done—there was nothing more to add (or rather, remove), so development was stopped (or rather, paused).

Re:PuTTY 0.61 released by cbs on Wednesday July 13, 2011 @02:00PM (#2759860)
I didn't say anything about superfluous features.

Done in the software world doesn't really mean "done", just that its not being working on. Putty wasn't done, there was a list of bugs sitting there waiting to be addressed. But thats not my point, even at its peak of development, putty never had more than 4 releases within a year.