The new forums will be named Coin Return (based on the most recent
vote)! You can check on the status and timeline of the transition to the new forums
here.
The Guiding Principles and New Rules
document is now in effect.
[Programming] Page overflow to new thread
Posts
Long as hell branches with multiple mainline merges ( or even worse spider merges into them ) just suck.
Like everything else KISS.
If you want a clean commit history, make a pretty commit message when you squash everything into a single merge commit.
The fact that rebase is a feature that only does what it’s supposed to during a specific phase of the lifecycle of a branch, and ruins things for everybody when used after that point, but is in no way documented as such nor constrained by any sort of controls to prevent you from making all your colleagues’ lives worse with a ton of force pushes and history changing, is peak git IMO.
Your Ad Here! Reasonable Rates!
a) you shouldn't have long lived feature branches anyway so virtually nothing should be hanging off extant branches. Release branches can get cherry-picked to
b) you should really be using something like gerrit rather than force pushing and you can just run it in rebase/cherry-pick mode which does all of this automatically
c) there's little value in all the intermediate "quick fix" "forgot a file" commits that you lose in amend/rebase workflows
“Oh cool! What does your architecture do when the database goes down?”
Every time I was hoping to meet someone who was doing cool things with distributed systems. Without fail, I got instead an uncomfortable silence and a new conversation partner.
Your Ad Here! Reasonable Rates!
The difference between "we're migrating to a microservices architecture because it solves a clear problem we have" and "we're migrating to a microservices architecture because our CEO/CTO/tech lead* read a white paper over the weekend."
*I know we prefer to roast non-technical management but never underestimate the ability of devs to be self-destructive