-
Notifications
You must be signed in to change notification settings - Fork 485
Mob‐Programming Sessions
Lukas Krause edited this page Aug 18, 2026
·
1 revision
This wiki page documents how we run mob-programming sessions.
To give everyone a clear picture of how we run mob-programming sessions, here are a couple of rules we follow:
-
Everyone participating in the session should take the time to familiarize themselves as well as possible with the context beforehand.
-
There is always one driver who writes code and performs all other necessary actions (such as making Git commits). The rest of the mob navigates the driver by telling them what to execute.
-
Roles switch regularly every 30 minutes.
-
A 15-minute break is taken after every 60 minutes (after every second role switch).
-
Code is shared via a branch on the upstream repository.
- Development Environment Overview
- Development Environment Tips & Tricks
- Spec-Tips
- Code Style
- Rubocop
- Testing with VCR
- Test in kanku
- Authentication
- Authorization
- Autocomplete
- BS Requests
- Events
- ProjectLog
- Notifications
- Feature Toggles
- Build Results
- Attrib classes
- Flags
- The BackendPackage Cache
- Maintenance classes
- Cloud uploader
- Delayed Jobs
- Staging Workflow
- StatusHistory
- OBS API
- Owner Search
- Search
- Links
- Distributions
- Repository
- Data Migrations
- Package Versions
- Rails Update
- Ruby Update
- Updating-rake-or-rack
- Brakeman
- Run OpenQA smoketest locally
- Factory Dashboard
- Responsive Guidelines
- osc
- Importing database dumps
- Problem Statement & Solution
- Kickoff New Stuff
- Mob-Programming Sessions
- New Swagger API doc
- Documentation and Communication
- GitHub Actions
- Setup an OBS Development Environment on macOS
- Remote Pairing Setup Guide
- How to Introduce Software Design Patterns
- Query Objects
- Services
- View Components
- RFC: Core Components
- RFC: Decorator Pattern
- RFC: Backend models
- RFC: Hotwire Turbo Frames Pattern