Common Development Terminology
Software teams use a lot of shorthand: words like sprint, blocker, merge, endpoint or regression. You need the common ones to follow meetings, tickets and code reviews without guessing.
Where to find the words
This site has a glossary with short definitions grouped by theme: source control, process and agile, development, quality, operations, security, infrastructure and more. Use it for quick lookups. Each topic page goes deeper on the ideas behind the words.
Why terms cause confusion
- Words have several meanings. “Environment” can mean a deployment target, your shell settings or a virtual environment. “Service”, “model” and “pipeline” are similar. Context decides.
- Teams bend definitions. One team’s “done” means merged, another’s means released. A “sprint” may be two weeks or three. Check the local meaning, and ask when unsure.
- Abbreviations pile up: PR, CI/CD, SLA, MVP, PoC, WIP, LGTM. Companies add their own on top.
- Casual use hides precision. “It’s broken” could be a bug, a misconfiguration or a missing feature. Precise words (defect, regression, outage, flaky test) narrow it down.
Learning vocabulary on the job
- Keep a personal list of terms you hear and could not explain. Look each one up the same day.
- Ask in the moment when it is cheap: “When you say X here, do you mean Y?” Experienced people usually appreciate the check, and others in the room often had the same question.
- Explain a term in your own words, with an example from your own project. If you can do that, you know it.
- Use terms carefully. Repeating a word you have not understood can mislead others.
Pairs and related topics
- Many terms come as pairs that are easy to mix up: authentication vs authorization, build vs deploy, bug vs feature request, merge vs rebase.
- Naming matters in code too; see Clean Code and Naming.
- Process words such as story, epic and Definition of Done are covered in Agile, Scrum, and Kanban.
Try it
Open the glossary and pick ten terms you have heard but could not explain well. Write a one-sentence explanation of each in your own words, then compare with the definition and fix any differences. Pick one term from the next meeting you attend and add it to your list.
Common mistakes
- Repeating a term you have not understood.
- Assuming your team's meaning of "done" or "sprint" matches everyone else's.
- Saying "it's broken" when a precise word (defect, regression, outage) would help.
Check yourself
- Why can the word "environment" cause confusion?
- Which pairs of terms are easy to mix up?