cm0002@lemmy.world to Programmer Humor@programming.dev · 3か月前Junior Prompt Engineeringlemmy.mlimagemessage-square54fedilinkarrow-up1766arrow-down18
arrow-up1758arrow-down1imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 3か月前message-square54fedilink
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up19·edit-23か月前What, like some kind of design requirements? Heresy!
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up9arrow-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-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.
minus-squarepsud@aussie.zonelinkfedilinkEnglisharrow-up2·3か月前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