Programmer Humor

27182 readers

1262 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

754

submitted 7 months 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

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

What, like some kind of design requirements?

Heresy!

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

Design requirements are too ambiguous.

[–] spankmonkey@lemmy.world 10 points 7 months ago

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

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

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

Our designs are usually unambiguous