@[email protected] to Programmer [email protected] • 3 days agoJunior Prompt Engineeringlemmy.mlimagemessage-square52fedilinkarrow-up1737arrow-down18cross-posted to: [email protected]
arrow-up1729arrow-down1imageJunior Prompt Engineeringlemmy.ml@[email protected] to Programmer [email protected] • 3 days agomessage-square52fedilinkcross-posted to: [email protected]
minus-squaresnooggumslinkfedilinkEnglish18•edit-23 days agoWhat, like some kind of design requirements? Heresy!
minus-squaresnooggumslinkfedilinkEnglish10•3 days agoDesign requirements are what it should do, not how it does it.
minus-square@[email protected]linkfedilinkEnglish2•2 days agoI’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts” Our designs are usually unambiguous
minus-square@[email protected]linkfedilink5•3 days agoThat’s why you must negotiate or clarify what is being asked. Once it has been accepted, it is not ambiguous anymore as long as you respect it.
What, like some kind of design requirements?
Heresy!
Design requirements are too ambiguous.
Design requirements are what it should do, not how it does it.
I’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts”
Our designs are usually unambiguous
That’s why you must negotiate or clarify what is being asked. Once it has been accepted, it is not ambiguous anymore as long as you respect it.