@cm0002@lemmy.world to Programmer Humor@programming.dev • 1 month agoJunior Prompt Engineeringlemmy.mlimagemessage-square53fedilinkarrow-up11arrow-down10cross-posted to: programmerhumor@lemmy.ml
arrow-up11arrow-down1imageJunior Prompt Engineeringlemmy.ml@cm0002@lemmy.world to Programmer Humor@programming.dev • 1 month agomessage-square53fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareBjörn Tantaulinkfedilink0•1 month agoIt would be nice if it was possible to describe perfectly what a program is supposed to do.
minus-squareOrvornlinkfedilink0•1 month agoSomeone should invent some kind of database of syntax, like a… code
minus-square@heavydust@sh.itjust.workslinkfedilink0•1 month agoBut it would need to be reliable with a syntax, like some kind of grammar.
minus-square@Knock_Knock_Lemmy_In@lemmy.worldlinkfedilink0•1 month agoWe don’t want anything amateur. It has to be a professional codegrammar.
minus-square@peoplebeproblems@midwest.sociallinkfedilinkEnglish0•1 month agoThat’s great, but then how do we know that the grammar matches what we want to do - with some sort of test?
minus-squareNatanaellinkfedilink0•1 month agoHow to we know what to test? Maybe with some kind of specification?
minus-square@maiskanzler@feddit.nllinkfedilink0•edit-21 month agoPeople could give things a name and write down what type of thing it is.
minus-squareRayquetzalcoatllinkfedilinkEnglish0•1 month agoI think our man meant in terms of real-world situations
minus-square@heavydust@sh.itjust.workslinkfedilink0•1 month agoAnd NOT yet another front page written in ReactJS.
minus-square@xthexder@l.sw0.comlinkfedilink0•edit-21 month agoThis still isn’t specific enough to specify exactly what the computer will do. There are an infinite number of python programs that could print Hello World in the terminal.
minus-square@Venator@lemmy.nzlinkfedilink0•1 month agoYeah but that’s a lot of writing. Much less effort to get the plagiarism machine to write it instead.
minus-square@peoplebeproblems@midwest.sociallinkfedilinkEnglish0•1 month agoHa None of us would have jobs
minus-squareMentalEdgelinkfedilink0•1 month agoI think the joke is that that is literally what coding, is.
minus-squaresnooggumslinkfedilinkEnglish0•edit-21 month agoWhat, like some kind of design requirements? Heresy!
minus-squaresnooggumslinkfedilinkEnglish0•1 month agoDesign requirements are what it should do, not how it does it.
minus-square@heavydust@sh.itjust.workslinkfedilink0•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-square@psud@aussie.zonelinkfedilinkEnglish0•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
It would be nice if it was possible to describe perfectly what a program is supposed to do.
Someone should invent some kind of database of syntax, like a… code
But it would need to be reliable with a syntax, like some kind of grammar.
A codegrammar?
We don’t want anything amateur. It has to be a professional codegrammar.
That’s great, but then how do we know that the grammar matches what we want to do - with some sort of test?
How to we know what to test? Maybe with some kind of specification?
People could give things a name and write down what type of thing it is.
What did you said?
I think our man meant in terms of real-world situations
And NOT yet another front page written in ReactJS.
This still isn’t specific enough to specify exactly what the computer will do. There are an infinite number of python programs that could print Hello World in the terminal.
I knew it, i should’ve asked for assembly
Yeah but that’s a lot of writing. Much less effort to get the plagiarism machine to write it instead.
Ha
None of us would have jobs
I think the joke is that that is literally what coding, is.
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