cm0002@lemmy.world to Programmer Humor@programming.dev · 1 年前Junior Prompt Engineeringlemmy.mlimagemessage-square53fedilinkarrow-up1762cross-posted to: programmerhumor@lemmy.ml
arrow-up1762imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 年前message-square53fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up19·edit-21 年前What, like some kind of design requirements? Heresy!
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up10·1 年前Design requirements are what it should do, not how it does it.
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up5·1 年前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.
minus-squarepsud@aussie.zonelinkfedilinkEnglisharrow-up2·1 年前I’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts” Our designs are usually unambiguous
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.
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.
I’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts”
Our designs are usually unambiguous