> When one talks about software, it’s common to start by listing out a program’s features. When it comes to acme, however, it’s perhaps more appropriate to star

> When one talks about software, it’s common to start by listing out a program’s features. When it comes to acme, however, it’s perhaps more appropriate to start by talking about what features it does not include. I think this assumes you do have an idea of the program you're building already, which means you already have idea of it's shape and featureset. I agree with the premise but I think you can't realistically start at "What don't we do". You still need to know what roughly you're building so you know what to take away.