732

submitted 9 months ago* (last edited 9 months ago) by agilob@programming.dev to c/programmer_humor@programming.dev

146 comments fedilink hide all child comments

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

[-] simple@lemm.ee 119 points 9 months ago

Having to go through the process of merging hurts morale and slows performance. Give everyone on your team the right to force push to master.

[-] NocturnalMorning@lemmy.world 36 points 9 months ago

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

[-] SpeakinTelnet@programming.dev 34 points 9 months ago

Keep everyone awake and on their toes.

[-] EatYouWell@lemmy.world 27 points 9 months ago

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

[-] SpeakinTelnet@programming.dev 12 points 9 months ago

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

[-] NocturnalMorning@lemmy.world 4 points 9 months 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.

[-] NocturnalMorning@lemmy.world 3 points 9 months ago* (last edited 9 months ago)

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

[-] eruchitanda@lemmy.world 2 points 9 months ago

Don't hurt their morale!

[-] MeanEYE@lemmy.world 1 points 9 months 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.