Collaboration Glossary
Browse 92 collaboration terms defined in plain English, from the cultural dictionary of computing.
92 Collaboration Terms
- AI Workspace
- A shared environment where teams can build, test, and manage AI assets such as prompts, datasets, evaluations, and model configurations. AI workspaces help...
- Brainstorm
- A session for generating ideas quickly and openly before narrowing them down. In tech teams brainstorming can be useful for exploration, though poorly run...
- Central Repository
- A main shared repository or source of record where code, documents, or assets are kept for team use. In culture discussions, the phrase often signals the need...
- Code Buddy
- A person paired with someone for coding support, feedback, accountability, or onboarding. The phrase is informal, but the idea is common in mentorship,...
- Code Pairing
- Working on code together in real time, often with one person typing and the other reviewing, questioning, or navigating. Code pairing is used for onboarding,...
- Code Review
- Code Review is the systematic examination of source code by one or more developers other than the author, aimed at finding bugs, improving code quality,...
- Code Review Culture
- The shared norms that determine how review is done, including tone, speed, rigor, mentoring expectations, and whether feedback improves the code or just slows...
- Code Session
- A period of focused time spent coding, alone or with others, often framed deliberately as a working block. In culture, the phrase often implies intentional...
- Code Sharing
- The practice of sharing code snippets, repositories, patterns, or libraries across teams or communities. Code sharing supports learning and reuse, though it...
- Code Sprint
- A short intensive period focused on making rapid coding progress, often with a narrow goal or event deadline. Code sprints are common in open source, internal...
- Code Submission
- The act of submitting code for review, assessment, integration, or publication. In practice, code submission processes shape team velocity, review quality, and...
- Co-Located Team
- A team that works primarily from the same physical location rather than being distributed across regions or remote setups. In culture discussions co-located...
- Commit Message
- The text attached to a version control commit that summarizes what changed and often why. Good commit messages are a strong cultural norm in healthy...
- CRDTs
- Conflict-free Replicated Data Types — data structures that can be replicated across multiple nodes and independently updated without coordination, with a...
- Cross-Functional Team
- A team made up of people from different functions such as engineering, design, product, operations, and support working toward a shared outcome....
- CryptPad
- A privacy-focused collaborative office and document suite designed to provide end-to-end encrypted editing and sharing. It is often referenced as an example of...
- Design Review
- A structured review of a design proposal, whether visual, technical, or interaction-focused, to surface issues and improve alignment before implementation. In...
- Design System Culture
- The norms a team or organization has around using, maintaining, and respecting a shared design system. Good design system culture balances consistency with...
- Digital Collaboration
- Working together through digital tools, documents, chat, video, and shared platforms rather than relying only on in-person coordination. In modern work culture...
- Domain Expert
- A person with deep knowledge of a specific business, technical, regulatory, or operational domain. In product and engineering culture, domain experts are often...
- Draft PR
- A pull request marked as not yet ready for final review or merge, often used to share work in progress, get early feedback, or make progress visible sooner. In...
- Embedded Team
- A team or person placed closely within another group or function so they can work with that group's needs directly rather than from a distant service model....
- Facilitation
- The practice of guiding a discussion or process so a group can think clearly, stay focused, and move toward a useful outcome. In work culture facilitation is...
- Feature Branch
- A short-lived Git branch created from the main branch to develop a single feature or fix in isolation. Merged back via pull request after code review and CI...
- Git Blame
- A Git Blame is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Branch
- A Git Branch is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Git Cherry-Pick
- A Git Cherry-Pick is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
- Git Clone
- A Git Clone is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Commit
- A Git Commit is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Git Config
- A Git Config is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Git Conflict
- A Git Conflict is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Git Culture
- The shared habits, expectations, and arguments a team has around using Git, including branching, rebasing, commit messages, reviews, and release flow. Git...
- Git Diff
- A Git Diff is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Flow
- A Git Flow is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Fork
- A Git Fork is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Grep
- A Git Grep is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git History
- A Git History is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Git Hook
- A Git Hook is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- GitHub Actions
- A GitHub Actions is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
- GitHub CLI
- A GitHub CLI is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- GitHub Codespaces
- A GitHub Codespaces is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
- GitHub Copilot
- A GitHub Copilot is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
- GitHub Pages
- A GitHub Pages is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- GitHub Pull Request
- A GitHub-specific pull request used to propose, review, discuss, and merge code changes. In modern software culture, the GitHub pull request is not just a tool...
- GitLab CI
- A GitLab CI is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Log
- A Git Log is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Merge
- A Git Merge is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Pull
- A Git Pull is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Push
- A Git Push is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Remote
- A Git Remote is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Git Reset
- A Git Reset is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Submodule
- A Git Submodule is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
- Git Tag
- A Git Tag is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
- Git Worktree
- A Git Worktree is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
- Hackathon
- An event where programmers, designers, and others collaborate intensively (typically 24-48 hours) to build a project from scratch. Originally a pure...
- Information Sharing
- The exchange of security-relevant data such as indicators, tactics, incident details, or lessons learned between teams, companies, sectors, or government...
- Inner Source
- The practice of applying open source development patterns inside a company, such as visible repositories, shared ownership, broad contribution rights, and...
- Intelligence Sharing
- The exchange of analyzed threat intelligence, not just raw indicators, between organizations or teams to improve collective defense. It usually includes...
- Mattermost
- An open-source team messaging platform often used as a self-hosted alternative to commercial workplace chat tools.
- Merge Conflict
- Merge Conflict occurs in version control when two branches have made competing changes to the same lines of a file, or when one branch deletes a file that the...
- Merge Request
- A proposed code change submitted for review and eventual merge, especially in GitLab-style workflows where the term parallels GitHub’s pull request. The name...
- Mob
- Short for mob programming or, more loosely, a whole group piling into the same coding or debugging session at once. It can be highly effective for shared...
- Mob Programming
- Mob Programming is a collaborative software development approach where the entire team works together on the same code, at the same time, using a single...
- Nextcloud
- A self-hosted collaboration platform for files, sharing, calendars, and related productivity features.
- Open Source Contributor
- A person who contributes code, documentation, triage, design, translations, or other work to an open source project. The term matters culturally because...
- Operational Transform
- An algorithm for maintaining consistency in collaborative editing by transforming concurrent operations against each other. When two users type at the same...
- Pair Debugging
- A debugging practice where two people investigate a problem together, combining context, observation, and reasoning in real time. It often works well for...
- Pair Programming
- Pair Programming is a software development technique where two programmers work together at a single workstation, with one typing (the driver) while the other...
- Pair Programming Culture
- A team norm where engineers frequently work together live on the same problem to share context, reduce mistakes, and teach one another.
- Peer Production
- A model of production in which large numbers of distributed participants collaboratively create shared goods without relying entirely on traditional...
- Peer Review
- Evaluation of work by colleagues with relevant expertise before it is accepted, published, or shipped. In software teams, peer review commonly means code...
- Ping Pong Programming
- A pairing style where one person writes a failing test, the other writes the code to pass it, and the roles keep alternating back and forth. It is closely...
- Popcorn Code Review
- A review style where comments, opinions, or walkthrough turns bounce rapidly between several people, like popcorn popping around the room. It can be energetic...
- PR Convention
- The agreed conventions a project uses for pull requests, such as title format, checklist expectations, review etiquette, or labeling rules. In collaborative...
- PR Review
- The process of reviewing a pull request for correctness, style, architecture, tests, and maintainability before merging. PR review is both a technical...
- PR Workflow
- The end-to-end process around creating, reviewing, updating, approving, and merging pull requests. In engineering culture, PR workflow quality strongly affects...
- Pull Request
- A proposal to merge changes from one branch into another, creating a space for code review, discussion, and automated checks. GitHub calls them 'pull...
- Purple Team
- A collaborative security practice that combines red team attack simulation with blue team defensive improvement. It shows up in application security, identity,...
- Rocket Chat
- An open-source team communication platform used as a self-hosted alternative to commercial chat systems.
- Screen Sharing
- The act of broadcasting one’s screen to others during a meeting, support session, or collaboration call. It became a core remote-work habit for debugging,...
- Social Coding
- A model of software development where coding activity is publicly visible, collaborative, and socially structured through pull requests, stars, forks,...
- Source Control
- A system that records changes to files over time so that specific versions can be recalled, compared, merged, and audited. Git is the dominant tool, enabling...
- Stone Soup
- A project or solution that starts with almost nothing and improves because many people each contribute something useful. In engineering slang, stone soup often...
- Team Kill
- A move that harms your own team, intentionally or not, borrowing from multiplayer game language. In engineering slang, team kills include surprise changes, bad...
- Three Amigos
- A small trio, often product, engineering, and design or QA, working closely to align on scope and behavior. In engineering slang, the three amigos pattern is...
- Three Amigos Meeting
- A planning or clarification meeting that brings together representatives such as product, engineering, and QA to align on a story before implementation.
- Two Heads
- A shorthand for the idea that two people thinking together can solve a problem better than one alone. In engineering slang, two heads often means pairing,...
- Version Control
- The practice and tooling for tracking changes to files over time, enabling developers to revert to previous states, work on parallel branches, and merge...
- Version Control Culture
- The norms around how a team uses version control, including commit hygiene, branching strategy, review discipline, merge practices, and historical readability....
- Version Control System
- Software that manages changes to a collection of files by recording each revision as a snapshot or set of diffs, supporting branching, merging, and history...
- Wiki
- A collaboratively editable website or knowledge base where users can create, revise, and link pages over time. In engineering organizations, wikis often serve...
- Working Group
- A group formed to work on a specific technical, organizational, or policy area within a larger project, foundation, or standards process. Working groups allow...
Related Topics
- Version Control (31 terms in common)
- Tooling (28 terms in common)
- Git (11 terms in common)
- Code Review (8 terms in common)
- Open Source (4 terms in common)
- Meetings (4 terms in common)
- Slang (4 terms in common)
- Teams (4 terms in common)
- Self Hosted (3 terms in common)
- Github (3 terms in common)
- Learning (3 terms in common)
- Chat (2 terms in common)
- Reviews (2 terms in common)
- Xp (2 terms in common)
- Quality (2 terms in common)
- Pair Programming (2 terms in common)
- Knowledge (2 terms in common)
- Workflow (2 terms in common)
- Coding (2 terms in common)
- Pull Requests (2 terms in common)