this post was submitted on 01 Apr 2025
728 points (98.9% liked)

Programmer Humor

22187 readers
1966 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
728
Junior Prompt Engineering (lemmy.ml)
submitted 2 days ago by cm0002@lemmy.world to c/programmer_humor@programming.dev
52 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 121 points 2 days ago (5 children)

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

[–] Venator@lemmy.nz 3 points 21 hours ago

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

[–] orvorn@slrpnk.net 81 points 2 days ago (1 children)

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

[–] heavydust@sh.itjust.works 37 points 2 days ago (2 children)

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

[–] peoplebeproblems@midwest.social 24 points 2 days 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 20 points 2 days ago (1 children)

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

[–] maiskanzler 1 points 1 day ago* (last edited 1 day ago)

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

[–] monkeyslikebananas2@lemmy.world 5 points 2 days ago (1 children)

A codegrammar?

[–] Knock_Knock_Lemmy_In@lemmy.world 9 points 2 days ago

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

[–] spankmonkey@lemmy.world 18 points 2 days ago* (last edited 2 days ago) (1 children)

What, like some kind of design requirements?

Heresy!

[–] bjoern_tantau@swg-empire.de 7 points 2 days ago (3 children)

Design requirements are too ambiguous.

[–] spankmonkey@lemmy.world 10 points 2 days ago

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

[–] psud@aussie.zone 2 points 1 day ago

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

Our designs are usually unambiguous

[–] heavydust@sh.itjust.works 5 points 2 days 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.

[–] drew_belloc@programming.dev 8 points 2 days ago (2 children)

What did you said?

[–] rayquetzalcoatl@lemmy.world 8 points 2 days ago (1 children)

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

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

And NOT yet another front page written in ReactJS.

[–] peoplebeproblems@midwest.social 1 points 2 days 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 1 day ago* (last edited 1 day 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 1 day ago

I knew it, i should've asked for assembly

[–] peoplebeproblems@midwest.social 1 points 2 days ago (1 children)

Ha

None of us would have jobs

[–] MentalEdge@sopuli.xyz 11 points 2 days ago

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