731

Merge then review(programming.dev)

posted
*
by
Avatar
agilob@programming.dev
in
Avatar
programmer_humor@programming.dev
146 comments
hidereport

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

Sort:
HotTopControversialNewOld
You are viewing a single thread.
View all comments View context
Avatar
NocturnalMorning@lemmy.world
36 points

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

permalink
report
parent
reply
Avatar
SpeakinTelnet@programming.dev
34 points

Keep everyone awake and on their toes.

permalink
report
parent
reply
Avatar
EatYouWell@lemmy.world
27 points

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

permalink
report
parent
reply
Avatar
SpeakinTelnet@programming.dev
12 points

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

permalink
report
parent
reply
Show more comments
Avatar
NocturnalMorning@lemmy.world
3 points
*

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

permalink
report
parent
reply
Avatar
chi-chan~@lemmy.world
2 points

Don’t hurt their morale!

permalink
report
parent
reply
Avatar
MeanEYE@lemmy.world
1 point

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.

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

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

Community stats

  • 3.7K

    Monthly active users

  • 1K

    Posts

  • 38K

    Comments

Community moderators