this post was submitted on 01 Apr 2025
757 points (99.0% liked)

Programmer Humor

22780 readers
686 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
757
Junior Prompt Engineering (lemmy.ml)
submitted 3 weeks ago by cm0002@lemmy.world to c/programmer_humor@programming.dev
54 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] bjoern_tantau@swg-empire.de 128 points 3 weeks ago (5 children)

It would be nice if it was possible to describe perfectly what a program is supposed to do.

[–] orvorn@slrpnk.net 86 points 3 weeks ago (1 children)

Someone should invent some kind of database of syntax, like a... code

[–] heavydust@sh.itjust.works 40 points 3 weeks ago (2 children)

But it would need to be reliable with a syntax, like some kind of grammar.

[–] peoplebeproblems@midwest.social 27 points 3 weeks ago (1 children)

That's great, but then how do we know that the grammar matches what we want to do - with some sort of test?

[–] Natanael@infosec.pub 23 points 3 weeks ago (1 children)

How to we know what to test? Maybe with some kind of specification?

[–] maiskanzler@feddit.nl 2 points 3 weeks ago* (last edited 3 weeks ago)

People could give things a name and write down what type of thing it is.

[–] monkeyslikebananas2@lemmy.world 5 points 3 weeks ago (1 children)

A codegrammar?

[–] Knock_Knock_Lemmy_In@lemmy.world 11 points 3 weeks ago

We don't want anything amateur. It has to be a professional codegrammar.

[–] spankmonkey@lemmy.world 19 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

What, like some kind of design requirements?

Heresy!

[–] bjoern_tantau@swg-empire.de 8 points 3 weeks ago (3 children)

Design requirements are too ambiguous.

[–] spankmonkey@lemmy.world 10 points 3 weeks ago

Design requirements are what it should do, not how it does it.

[–] heavydust@sh.itjust.works 5 points 3 weeks ago

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.

[–] psud@aussie.zone 2 points 3 weeks ago

I'm a systems analyst, or in agile terminology "a designer" as I'm responsible for "design artifacts"

Our designs are usually unambiguous

[–] drew_belloc@programming.dev 9 points 3 weeks ago (2 children)

What did you said?

[–] rayquetzalcoatl@lemmy.world 8 points 3 weeks ago (1 children)

I think our man meant in terms of real-world situations

[–] heavydust@sh.itjust.works 2 points 3 weeks ago (1 children)

And NOT yet another front page written in ReactJS.

[–] peoplebeproblems@midwest.social 1 points 3 weeks ago

Oh, well, that's good, because I have a ton of people who work with Angular and not React.

[–] xthexder@l.sw0.com 5 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

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.

[–] drew_belloc@programming.dev 2 points 3 weeks ago

I knew it, i should've asked for assembly

[–] Venator@lemmy.nz 3 points 3 weeks ago

Yeah but that's a lot of writing. Much less effort to get the plagiarism machine to write it instead.

[–] peoplebeproblems@midwest.social 1 points 3 weeks ago (1 children)

Ha

None of us would have jobs

[–] MentalEdge@sopuli.xyz 11 points 3 weeks ago

I think the joke is that that is literally what coding, is.