cm0002@lemmy.world to Programmer Humor@programming.dev · 3 天前Junior Prompt Engineeringlemmy.mlimagemessage-square52fedilinkarrow-up1743arrow-down18cross-posted to: [email protected]
arrow-up1735arrow-down1imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 3 天前message-square52fedilinkcross-posted to: [email protected]
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up18·edit-23 天前What, like some kind of design requirements? Heresy!
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up8arrow-down1·3 天前Design requirements are too ambiguous.
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up10·3 天前Design requirements are what it should do, not how it does it.
minus-squarepsud@aussie.zonelinkfedilinkEnglisharrow-up2·2 天前I’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-up5·3 天前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.
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.