cm0002@lemmy.world to Programmer Humor@programming.dev · 4 days agoJunior Prompt Engineeringlemmy.mlexternal-linkmessage-square51fedilinkarrow-up11arrow-down10cross-posted to: programmerhumor@lemmy.ml
arrow-up11arrow-down1external-linkJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 4 days agomessage-square51fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up0·4 days agoDesign requirements are too ambiguous.
minus-squarepsud@aussie.zonelinkfedilinkEnglisharrow-up0·3 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-squareheavydust@sh.itjust.workslinkfedilinkarrow-up0·4 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.
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up0·4 days agoDesign requirements are what it should do, not how it does it.
Design requirements are too ambiguous.
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.
Design requirements are what it should do, not how it does it.