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

Programmer Humor

19503 readers
339 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
732
Merge then review (programming.dev)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

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
[–] [email protected] 36 points 1 year ago (3 children)

Yes, especially the newbies who don't know what they're doing.

[–] [email protected] 34 points 1 year ago (1 children)

Keep everyone awake and on their toes.

[–] [email protected] 27 points 1 year ago (2 children)

You're not truly part of the team until you cause a massive outage.

[–] [email protected] 12 points 1 year ago (1 children)

New employees are responsible of at least 75℅ of documentation clarification and process overhaul.

[–] [email protected] 4 points 1 year ago

I'm totally on board with process overhaul. Ours was stupid when I started, I said it was stupid, and nothing changed. If someone else comes in and can say it's stupid more convincingly than me, that's great.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

Who me? No, must be someone else with my name you're thinking of.

[–] [email protected] 2 points 1 year ago

Don't hurt their morale!

[–] [email protected] 1 points 1 year ago

I honestly wouldn't see this as a problem. But if you break something it's up to you to fix it. But we also don't do CI. We release features in batches after they have been tested and seen to be working.