this post was submitted on 01 Apr 2025

760 points (99.0% liked)

Programmer Humor

programmer_humor@programming.dev

33,695 readers

7,833 active

953 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.

founded 3 years ago

moderators

anzo@programming.dev

Feyter@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

Junior Prompt Engineering (lemmy.ml)

submitted 2 years ago by cm0002@lemmy.world to c/programmer_humor@programming.dev

53 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] spankmonkey@lemmy.world 19 points 2 years ago* (4 children)

What, like some kind of design requirements?

Heresy!

parent

hideshow 4 child comments

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

Design requirements are too ambiguous.

parent

hideshow 3 child comments

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

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

parent

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

parent

[–] psud@aussie.zone 2 points 2 years ago

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

Our designs are usually unambiguous

parent