Branching Paths - The Daily WTF
Feature Articles
Most Recent Articles
Branching Paths
The Crossroads
A More Civilized Age
Lose Some Padding
The Hard Goodbye
Classic WTF: My Many Girlfriends
Classic WTF: Server Room Fans and More Fun
The Easy No
CodeSOD
Most Recent Articles
Public Private Partnership
Connection State
Always Take the Option
Negative Days
Convert Back, Way Back
Classic WTF: Fork and Log
Classic WTF: The Table Selector
Wait Longer
Error'd
Most Recent Articles
Time Wounds All Heels
I Believe In Lingonberries
The Song that Never Ends?
Princess Pricing
Einfach so
Kaids Hen 2025
Fi fa foe
Microbits
Forums
Other Articles
Random Article
Other Series
Alex's Soapbox
Announcements
Best of…
Best of Email
Best of the Sidebar
Bring Your Own Code
Coded Smorgasbord
Mandatory Fun Day
Off Topic
Representative Line
News Roundup
Editor's Soapbox
Software on the Rocks
Souvenir Potpourri
Sponsor Post
Tales from the Interview
The Daily WTF: Live
Virtudyne
feature articles
codesod
error'd
forums
other articles
random article
Branching Paths
by Remy Porter<br>in Feature Articles<br>on 2026-08-12<br>Edit
Remy Porter<br>Computers were a mistake, so I accidentally became a farmer? Editor-in-Chief for TDWTF.
"You submitted a pull request."
Indika was, in fact, reviewing the comments she'd gotten on that very same pull request, when her boss, Bill, walked up behind her. What she didn't understand is why Bill said it like it was an accusation.
"Yes?" she replied.
"Okay, well, we don't do that here. You're new, so I'll let it slide, but please review the developer guide."
Well, Indika had reviewed the developer guide, or at least thought she had. As it turned out, there was the official, company wide developer guide. That's the one she'd read. But Bill maintained his own, for his team. He hadn't ever told her about it, but apparently assumed she'd have the oracular blessings of Apollo and find it by herself.
It had this to say:
Branching is prohibited. Merging is a time wasting activity and goes against CI principles. Only use git to commit, push, and pull.
And rebase, presumably, if everyone was just committing on the main branch?
Indika asked one of her co-workers, Elise, over coffee: "Is this real?"
"Yeah," Elise said. "I'm not sure how he found out about your PR, I don't think anybody added him to the review. I mean, why would they?"
"Oh, I sent him the link," Indika said. "Just a whole, 'I'm new here, look at me doing the work!' type heads up."
"Oh yeah, definitely don't do that."
"So we do use PRs?"
Elise nodded. "Of course we do. We're not crazy. We just make sure Bill never finds out."
That seemed like a terrible way to work, but Indika went along with it, at least for a few weeks. Then an opportunity presented itself; she and Bill bumped into each other in the kitchenette grabbing coffee, and nobody else was around. At this point, Indika had already submitted a number of PRs without Bill knowing.
"Bill, I've been meaning to ask, what's your rationale for prohibiting branching?"
Bill loved being asked that question. "Well, well, it comes from twenty years of experience. What exactly does a branch get you?"
"A distinct history of changes that can be maintained and eventually merged in once a large unit of work has been done without disrupting other work that might be in flight?"
"Another point of conflict! A chance for the code you're working on to get stale. A chance to fall behind the rest of the team. Now, for a large open source team, with a lot of collaborators, a branch might make sense. I'm skeptical, but I can at least understand it. But for our internal team? It's just developers seeing a new toy and going, 'oh, shiny!'"
Indika sipped her coffee and went back to her desk. She was fortunate to have a window nearby, and looked at the squirrels playing in the branches of the tree.
[Advertisement] Plan Your .NET 9 Migration with Confidence<br>Your journey to .NET 9 is more than just one decision.Avoid migration migraines with the advice in this free guide. Download Free Guide Now!
View all 7 comments "
" Public Private Partnership
Contact<br>Privacy Policy<br>RSS
Copyright © 2026 Inedo Publishing - v2024.9
Monitored by Panopta<br>• Deployed with BuildMaster