Programmer Humor

31992 readers

529 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 3 years ago

MODERATORS

anzo@programming.dev

Feyter@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

123

Boys, don't dev alone or you'll end up with a git log like mine (lemmy.world)

submitted 4 days ago* (last edited 4 days ago) by Gonzako@lemmy.world to c/programmer_humor@programming.dev

78 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Evotech@lemmy.world 3 points 3 days ago* (last edited 3 days ago) (2 children)

Yea you always work on main on the same project.

You don’t push broken code. You always need to keep mainline healthy

It takes some special considerations, but the benefits are great.

[–] kewjo@lemmy.world 2 points 3 days ago (1 children)

so when something breaks both devs, the one who made the previous change and the person pushing new, have to work together to solve the issue? no PRs or is everything a fork? do you revert and rebase every change?

[–] Evotech@lemmy.world 3 points 3 days ago* (last edited 3 days ago)

You revert the broken commit usually.

https://martinfowler.com/articles/continuousIntegration.html

This is a good article on the topic

[–] exu@feditown.com 1 points 3 days ago

That doesn't stop you from removing your test commits before pushing