3 ms·
> Imo, the trouble starts with the term "requirements." > There's an old joke about posting requirements to a job site: "(1) awesome webapp (2) really useful (
by hulitu 5y ago
> Imo, the trouble starts with the term "requirements."
> There's an old joke about posting requirements to a job site: "(1) awesome webapp (2) really useful (3) must make me a billion dollars.
> The requirements problem is like that.
Yeah. Someone, in the history of SW had a great idea: requirements must be atomic.
That's why a lot of products break when they are put together.
> Requirements are "gathered." Reality doesn't work like that. They aren't gathered. They're invented. a collection of requirements adds up to a design. Thinking of it as a bunch of requirements leads to designed by committee problems.
They are gathered. They are however, not a collection. They depend on each other. And when this depenfence is missing or left over the engineer will invent it to compensate for the lack of it. Every engineer. In its own way.
> Designers need to know the problem space, the materials, etc. The requirements part can't be separated from those, which is exactly what the concept promotes.
True. But "requirements must be atomic" :(
- dalbasal 5y agoThis may be true in an abstract sense, but not in the RW context that this post is dwelling in. Requirements in the sense that a customer or higher up might negotiate with a PM aren't atomic like that. Imo, this is a lot like an engineer blaming the spec and/or demanding a better spec. They're asking to be given a perfect task.
- hobs 5y agoIf everyone has slosh in their expectations budget, its ok, but if people want some undefinable thing and they know it when they see it and they get mad when they don't get it, you're going to get engineers asking for the "perfect spec" - because that's what they are effectively held accountable to.
- toshk 5y agoNot so much perfect spec. But hidden assumptions