cm0002@lemmy.world to Programmer Humor@programming.dev · 1 month agoJunior Prompt Engineeringlemmy.mlimagemessage-square54linkfedilinkarrow-up1765arrow-down18
arrow-up1757arrow-down1imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 month agomessage-square54linkfedilink
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up19·edit-21 month agoWhat, like some kind of design requirements? Heresy!
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up9arrow-down1·1 month agoDesign requirements are too ambiguous.
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up10·1 month agoDesign requirements are what it should do, not how it does it.
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up5·1 month 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-squarepsud@aussie.zonelinkfedilinkEnglisharrow-up2·1 month agoI’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