News for hackers. Stuff that matters.
Re:The Carrying-Cost of Code: Taking Lean Seriously by mberning on Wednesday May 18, 2011 @08:59AM (#2559970)
This is great from an engineering standpoint, but I would really like to meet a sales guy that would be willing to support this. It's very hard to tell a potential customer, in a nicer way of course, "We don't currently do X, Y, and Z, and we have no future plans to". Sales opportunities are where many of the ill conceived and infrequently used features in a product come from.
Re:The Carrying-Cost of Code: Taking Lean Seriously by quanticle on Wednesday May 18, 2011 @09:30AM (#2560063)
Apple seems to get away with it all the time. For example, look at Steve Jobs' keynote where he presented Snow Leopard. He turned '0 New Features' into a selling point.
Re:The Carrying-Cost of Code: Taking Lean Seriously by mberning on Wednesday May 18, 2011 @09:54AM (#2560134)
They do to an extent. The original iPhone lacked many 'non-essential' features that were later added.
Re:The Carrying-Cost of Code: Taking Lean Seriously by michaelfeathers on Wednesday May 18, 2011 @09:15AM (#2560019)
That's typical in companies that are seeking market. Afterward, you're more likely to have a product manager calling the shots, and they often decide against features for various reasons.

The fact of the matter is that companies can make these sorts of choices. It may be hard, but it isn't impossible.

Re:The Carrying-Cost of Code: Taking Lean Seriously by mberning on Wednesday May 18, 2011 @09:57AM (#2560142)
Precisely. When you NEED that next sale to stay alive it is near impossible to justify saying 'No' to the potential customer.

In my experience though, once you make it a habit of adding features to placate prospects, it is a very hard habit to shake.