cm0002@lemmy.world to Programmer Humor@programming.dev · 28 days agoJunior Prompt Engineeringlemmy.mlimagemessage-square54fedilinkarrow-up1765arrow-down18
arrow-up1757arrow-down1imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 28 days agomessage-square54fedilink
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up128·28 days agoIt would be nice if it was possible to describe perfectly what a program is supposed to do.
minus-squareOrvorn@slrpnk.netlinkfedilinkarrow-up86·28 days agoSomeone should invent some kind of database of syntax, like a… code
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up40·28 days agoBut it would need to be reliable with a syntax, like some kind of grammar.
minus-squarepeoplebeproblems@midwest.sociallinkfedilinkEnglisharrow-up27·28 days agoThat’s great, but then how do we know that the grammar matches what we want to do - with some sort of test?
minus-squareNatanael@infosec.publinkfedilinkarrow-up23·28 days agoHow to we know what to test? Maybe with some kind of specification?
minus-squaremaiskanzler@feddit.nllinkfedilinkarrow-up2·edit-227 days agoPeople could give things a name and write down what type of thing it is.
minus-squareKnock_Knock_Lemmy_In@lemmy.worldlinkfedilinkarrow-up11·28 days agoWe don’t want anything amateur. It has to be a professional codegrammar.
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up19·edit-228 days agoWhat, like some kind of design requirements? Heresy!
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up9arrow-down1·28 days agoDesign requirements are too ambiguous.
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up10·28 days agoDesign requirements are what it should do, not how it does it.
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up5·28 days 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·27 days agoI’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts” Our designs are usually unambiguous
minus-squareDrew Belloc@programming.devlinkfedilinkarrow-up17arrow-down8·28 days agoWhat did you said?
minus-squareRayquetzalcoatl@lemmy.worldlinkfedilinkEnglisharrow-up8·28 days agoI think our man meant in terms of real-world situations
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up2·28 days agoAnd NOT yet another front page written in ReactJS.
minus-squarepeoplebeproblems@midwest.sociallinkfedilinkEnglisharrow-up1·28 days agoOh, well, that’s good, because I have a ton of people who work with Angular and not React.
minus-squarexthexder@l.sw0.comlinkfedilinkarrow-up5·edit-228 days 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-squareDrew Belloc@programming.devlinkfedilinkarrow-up2·27 days agoI knew it, i should’ve asked for assembly
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up3·26 days agoYeah but that’s a lot of writing. Much less effort to get the plagiarism machine to write it instead.
minus-squarepeoplebeproblems@midwest.sociallinkfedilinkEnglisharrow-up1·28 days agoHa None of us would have jobs
minus-squareMentalEdge@sopuli.xyzlinkfedilinkarrow-up11·28 days agoI think the joke is that that is literally what coding, is.
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.
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.
A codegrammar?
We don’t want anything amateur. It has to be a professional codegrammar.
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
What did you said?
I think our man meant in terms of real-world situations
And NOT yet another front page written in ReactJS.
Oh, well, that’s good, because I have a ton of people who work with Angular and not React.
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.