<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Collaboration on Work You Can Explain</title>
		<link>https://workyoucanexplain.com/tags/collaboration/</link>
		<description>Recent content in Collaboration on Work You Can Explain</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
			<copyright>Copyright © Work You Can Explain</copyright>
		
		
			<lastBuildDate>Sun, 26 Jul 2026 00:00:00 -0500</lastBuildDate>
		
			<atom:link href="https://workyoucanexplain.com/tags/collaboration/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Use Git Worktrees for Parallel AI Agents</title>
				<link>https://workyoucanexplain.com/posts/git-worktrees-for-parallel-ai-agents/</link>
				<pubDate>Sun, 26 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/git-worktrees-for-parallel-ai-agents/</guid>
				<description>&lt;p&gt;Use Git worktrees for parallel AI agents only when the tasks can be separated&#xA;clearly. Create one branch and linked working directory per task, assign&#xA;exclusive files or responsibilities, inspect each result independently, and&#xA;integrate one commit at a time.&lt;/p&gt;&#xA;&lt;p&gt;Worktrees reduce interference between working directories. They do not make&#xA;overlapping designs, stale assumptions, or conflicting recommendations safe.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understand-what-a-worktree-isolates&#34;&gt;Understand what a worktree isolates&lt;/h2&gt;&#xA;&lt;p&gt;The official &lt;a href=&#34;https://git-scm.com/docs/git-worktree.html&#34;&gt;&lt;code&gt;git worktree&lt;/code&gt;&#xA;documentation&lt;/a&gt; states that one&#xA;repository can support multiple working trees and have more than one branch&#xA;checked out at a time.&lt;/p&gt;</description>
			</item>
			<item>
				<title>GitHub Is More Than Online Storage</title>
				<link>https://workyoucanexplain.com/posts/github-is-more-than-online-storage/</link>
				<pubDate>Fri, 24 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/github-is-more-than-online-storage/</guid>
				<description>&lt;p&gt;GitHub can store a remote copy of a Git repository, but its larger role is&#xA;collaboration around that repository. It adds access controls, issues, pull&#xA;requests, review, automation, releases, and project presentation.&lt;/p&gt;&#xA;&lt;h2 id=&#34;separate-git-from-github&#34;&gt;Separate Git from GitHub&lt;/h2&gt;&#xA;&lt;p&gt;Git records repository history locally. GitHub hosts repositories and services&#xA;around them. A remote is a named location used to exchange repository data; it&#xA;is not the only valid copy and does not replace a tested backup.&lt;/p&gt;</description>
			</item>
			<item>
				<title>When Notion Is the Better Tool</title>
				<link>https://workyoucanexplain.com/posts/when-notion-is-the-better-tool/</link>
				<pubDate>Fri, 24 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/when-notion-is-the-better-tool/</guid>
				<description>&lt;p&gt;Notion is a strong fit when several people need to update one structured source&#xA;and see it in different ways. A group project, club, or student organization may&#xA;need tasks by owner, deadlines by calendar, unresolved work by status, and&#xA;discussion attached to the work.&lt;/p&gt;&#xA;&lt;p&gt;If one person is taking personal concept notes, that collaboration model may add&#xA;unnecessary account and maintenance obligations.&lt;/p&gt;&#xA;&lt;h2 id=&#34;look-for-a-shared-state-problem&#34;&gt;Look for a shared-state problem&lt;/h2&gt;&#xA;&lt;p&gt;Use Notion when the work has most of these conditions:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your First Merge Conflict Should Be Deliberate</title>
				<link>https://workyoucanexplain.com/posts/your-first-merge-conflict-should-be-deliberate/</link>
				<pubDate>Fri, 24 Jul 2026 00:00:00 -0500</pubDate>
				<guid>https://workyoucanexplain.com/posts/your-first-merge-conflict-should-be-deliberate/</guid>
				<description>&lt;p&gt;A merge conflict is Git asking a person to decide how overlapping changes should&#xA;combine. Practice once in a disposable repository, with a clean working tree,&#xA;before deadlines or team work make the decision stressful.&lt;/p&gt;&#xA;&lt;h2 id=&#34;create-a-controlled-conflict&#34;&gt;Create a controlled conflict&lt;/h2&gt;&#xA;&lt;p&gt;Use a new practice repository with no important files. Commands assume a recent&#xA;Git installation and a default branch named &lt;code&gt;main&lt;/code&gt;; adjust the branch name only&#xA;if your repository uses another one.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
