this post was submitted on 14 Nov 2023
731 points (97.0% liked)

Programmer Humor

19302 readers
1303 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 1 year ago
MODERATORS
731
Merge then review (programming.dev)
submitted 10 months ago* (last edited 10 months ago) by agilob@programming.dev to c/programmer_humor@programming.dev
 

Move fast and break things.
Merge vulnerabilities.
Double the work.
Merge code without tests.
Anything, but don't let code become stale.

you are viewing a single comment's thread
view the rest of the comments
[–] silencioso@lemmy.world 20 points 10 months ago (9 children)

Before everyone loses their minds, in Extreme Programming there are safeguards other than PR reviews. Before you submit a PR, you are supposed to have written the tests and to have written your code with pair programming, so your code already has some safety measures in place. On top of that, when you merge and deploy, more tests are run, and only if all of them are green do your changes go into production.

[–] agilob@programming.dev 5 points 10 months ago (3 children)

you are supposed to have written the tests and to have written your code with pair programming,

I commented out the tests because they were failing, pipelines were green so I merged. Now it's running on prod. What do you do?

[–] silencioso@lemmy.world 16 points 10 months ago

Fire you for destroying the tests. It's intentional sabotage.

[–] pomodoro_longbreak@sh.itjust.works 6 points 10 months ago

Give you public kudos for moving fast and breaking things. We need more fearless cowboys like you around here

[–] Blackthorn@programming.dev 1 points 10 months ago

I would fire you for incompetence and sabotage. Problem solved.

load more comments (5 replies)