My comment to the author of this article was _not_ to blame, but to show that every party to software development ends up with unflattering characterizations of each other.
He didn't print the ones of non-developers I metnioned, but we're reading some of those right here.
To say that developers 'don't get it' often with requirements is not asinine -- it's obvious. Some times the reason is because those requirements don't make any sense. Sometimes they are too vague...
Sometimes I don't get what my wife says... That doesn't make me stupid, but given that fact, we both owe each other the time and effort to establish understanding.
So it's not about blame; it's about the responsibility on everyone's part to resolve misunderstandings before they become "bugs" in software. That is a core message of our company and its product, LISA.
> Translation: It's not our fault the developers couldn't understand our brick of a business case.
My Actual Meaning: It's no one's fault but everyone's responsibility that requirements are not understood in translation between the business and technologists.
Been married for years and haven't figured my wife out yet. Best I can do is work hard to understand her. In software, we have a similar problem.
My goal is/was not blame, but to show the shared responsibility.
Slashdot Mirror
He didn't print the ones of non-developers I metnioned, but we're reading some of those right here.
To say that developers 'don't get it' often with requirements is not asinine -- it's obvious. Some times the reason is because those requirements don't make any sense. Sometimes they are too vague...
Sometimes I don't get what my wife says... That doesn't make me stupid, but given that fact, we both owe each other the time and effort to establish understanding.
So it's not about blame; it's about the responsibility on everyone's part to resolve misunderstandings before they become "bugs" in software. That is a core message of our company and its product, LISA.
I don't think we disagree.
My Actual Meaning: It's no one's fault but everyone's responsibility that requirements are not understood in translation between the business and technologists.
Been married for years and haven't figured my wife out yet. Best I can do is work hard to understand her. In software, we have a similar problem.
My goal is/was not blame, but to show the shared responsibility.