cm0002@lemmy.world to Programmer Humor@programming.dev · 3 天前Junior Prompt Engineeringlemmy.mlimagemessage-square52fedilinkarrow-up1744arrow-down18
arrow-up1736arrow-down1imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 3 天前message-square52fedilink
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up122·3 天前It would be nice if it was possible to describe perfectly what a program is supposed to do.
minus-squareOrvorn@slrpnk.netlinkfedilinkarrow-up82·3 天前Someone should invent some kind of database of syntax, like a… code
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up38·3 天前But it would need to be reliable with a syntax, like some kind of grammar.
minus-squarepeoplebeproblems@midwest.sociallinkfedilinkEnglisharrow-up25·3 天前That’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-up21·3 天前How to we know what to test? Maybe with some kind of specification?
minus-squaremaiskanzler@feddit.nllinkfedilinkarrow-up1·edit-22 天前People could give things a name and write down what type of thing it is.
minus-squareKnock_Knock_Lemmy_In@lemmy.worldlinkfedilinkarrow-up9·3 天前We don’t want anything amateur. It has to be a professional codegrammar.
minus-squareVenator@lemmy.nzlinkfedilinkarrow-up3·2 天前Yeah but that’s a lot of writing. Much less effort to get the plagiarism machine to write it instead.
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.
minus-squareRayquetzalcoatl@lemmy.worldlinkfedilinkEnglisharrow-up8·3 天前I think our man meant in terms of real-world situations
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up2·3 天前And NOT yet another front page written in ReactJS.
minus-squarepeoplebeproblems@midwest.sociallinkfedilinkEnglisharrow-up1·3 天前Oh, 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-23 天前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.
minus-squareDrew Belloc@programming.devlinkfedilinkarrow-up2·3 天前I knew it, i should’ve asked for assembly
minus-squarepeoplebeproblems@midwest.sociallinkfedilinkEnglisharrow-up1·3 天前Ha None of us would have jobs
minus-squareMentalEdge@sopuli.xyzlinkfedilinkarrow-up11·3 天前I 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.
Yeah but that’s a lot of writing. Much less effort to get the plagiarism machine to write it instead.
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.
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
Ha
None of us would have jobs
I think the joke is that that is literally what coding, is.