733
Merge then review (programming.dev)
submitted 2 years ago* (last edited 2 years 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] 17 points 2 years ago

If you’re working in a context where it’s okay to make mistakes so long as they get fixed later, you’re not working on anything important.

[-] [email protected] 11 points 2 years ago* (last edited 2 years ago)

Honestly that's okay. That's how most of the games industry works and you know what? I sleep very well knowing that none of my code is actively hurting people. I do likely have some code in some defense simulator from my work on squad but so be it. Overall I make toys. Works of art and as long as the bugs are caught it really doesn't matter when. As long as it's before release. Even then you can just work at Bethesda and just never fix them no matter what.

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

Programmer Humor

23995 readers
1408 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