Programmer Humor

28241 readers

880 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

founded 2 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

507

tough choice? (infosec.pub)

submitted 3 days ago by 0x0@lemmy.zip to c/programmer_humor@programming.dev

74 comments fedilink hide all child comments

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

[–] GreenKnight23@lemmy.world 22 points 2 days ago (1 children)

Fortran. always Fortran.

because there's always more documentation than with vibecode.

[–] LeFantome@programming.dev 7 points 2 days ago (1 children)

Well obviously with vibe coded stuff, you just put the code back in the AI and ask for documentation.

Problem solved. /s

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

Your comment felt like it made my blood pressure spike, because I have heard people saying this 100% without irony

[–] NominatedNemesis@reddthat.com 1 points 1 day ago

Funny thing is, I would do that if there are no requirements, and the vibecode is unreadable. I would let the token-predictor create the requirements, after proof-reading and correcting it, I would create cooked-down list and run through a manager for approval, then rewrite it from scratch. My limited time and precious brain cells are too valuable to waste on reading and deciphering the half ton of sh!t an LLM produced.

If there are requirements (which are hardly applicable unfortunately) I would just rewrite the thing.