this post was submitted on 23 Jun 2026
126 points (92.6% liked)

Programmer Humor

32091 readers
489 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Evotech@lemmy.world 2 points 1 week ago (1 children)

Continuous integration is better. Fight me

[–] thoughtfuldragon@lemmy.blahaj.zone 6 points 1 week ago (1 children)

Nothing about continuous integration prevents you from using a branch to prepare your changes.

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

Yes, if you use feature branches its literally not continuous. It’s adjacent though.

Continuous Integration is a software development practice where each member of a team merges their changes into a codebase together with their colleagues changes at least daily

Meaning everything is in a version controlled mainline

People disagree about what CI is, but that’s the definition i subscribe to

[–] exu@feditown.com 2 points 1 week ago (2 children)

So does everyone work directly on main all the time? Do all of you work on the same project or are there multiple with one person per project? How do you work around the broken code your coworker just pushed so you can finish your tasks?

[–] Evotech@lemmy.world 3 points 1 week ago* (last edited 1 week 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 3 points 1 week 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 1 week ago* (last edited 1 week ago)

You revert the broken commit usually.

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

This is a good article on the topic

[–] exu@feditown.com 2 points 1 week ago

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

[–] Gonzako@lemmy.world 1 points 1 week ago

I personally make feature files. So if i'm working on FactorySeederModemLookupVector.ts someone elses could work on ☝️🥵🙏.php without bothering each other. Tho, my collabs have been ones with a LOT of communication.