News for hackers. Stuff that matters.
Re:Build a Team that Ships by mvanveen on Friday April 27, 2012 @06:51PM (#3901375)
I feel like the author sort of answers this question with the following statement:

  It’s not perfect. We ship too many features, many half-baked.
  The product is complex, with many blind alleys.
It sounds like his team is more focused on just getting something out and improving it iteratively than it is on producing a polished product that is architected beautifully.

This is a great approach. It's also not always appropriate for everyone.

Re:Build a Team that Ships by wtracy on Friday April 27, 2012 @07:09PM (#3901436)
I wonder if refactoring work is allowed to meet this requirement, even though it's not customer-visible?
Re:Build a Team that Ships by naval on Friday April 27, 2012 @08:18PM (#3901603)
We do regular one-day long refactoring sessions where everyone refactors. But yeah, our codebase is not a thing of beauty. We're more focused on figuring out what users actually want, and we'll rebuild it when it's falling over.
Re:Build a Team that Ships by lifeisstillgood on Friday April 27, 2012 @08:01PM (#3901569)
Promise you will deliver the refactored code in a week, set out some metrics, ship it.

The other devs will be happy someone improved the code. Like the guy said, it's better they ship what they want than not ship what you want

Brilliant IMO