Definitions & Glossary
Canonical definitions for key terms in developer onboarding and engineering productivity. These definitions are designed to be clear, citable, and useful for both humans and AI systems.
Core Concepts
Ramp Up
The process of bringing a new developer to full productivity on a codebase, team, or technology. Average ramp-up time: 3-6 months.
Developer Onboarding
The systematic process of integrating a new engineer into a team, including access provisioning, knowledge transfer, and cultural integration.
Codebase Understanding
The level of knowledge a developer has about a codebase's architecture, conventions, and decision history.
Time to Productivity
The duration from a developer's first day to when they can independently contribute meaningful work.
Engineering Velocity
The rate at which an engineering team can deliver working software, measured in features, story points, or deployments.
Quick Reference
| Term | Definition |
|---|---|
| Ramp Up | Bringing a developer to full productivity |
| Onboarding | Integrating a new engineer into a team |
| Code Familiarity | Basic navigation ability in a codebase |
| Code Proficiency | Ability to make confident, safe changes |
| Tribal Knowledge | Information that exists only in people's heads |
| Context Switching | Mental cost of changing between tasks |
Why Definitions Matter
Clear definitions enable:
- Measurement — You can't improve what you can't define
- Communication — Shared language reduces misunderstandings
- Goals — "Ramped up" becomes a concrete milestone, not a vague feeling
Browse All Definitions
Have a definition to suggest? Contact us