Every company's tool list looks intimidating from outside and obvious from inside. The trick is that the list is always the same shape.
There is a thing for tickets, a thing for code, a thing for documents, a thing for chat, and a thing for running the build. Learn one tool in each category properly and the others are dialects of it.
Learning Objectives
After this lesson, you will be able to:
Name the five tool categories every software company has something for
Use the ticket vocabulary correctly: assignee and reporter, workflow status, sprint and backlog
Follow a code change from a branch through a pull request to a release
Read an unfamiliar company's tool list and work out what each item is for
something that builds, tests and deploys automatically
somewhere documents and designs live
somewhere people talk
Learn one tool from each of those five properly. Everything else is a different arrangement of the same ideas, and you will pick it up in an afternoon.
This matters for job adverts too. A listing asking for Jira is describing the category. If you have used Linear seriously, you know what a workflow, a sprint and a backlog are, and that is what they were actually asking about.
The five categories, and what to learn in each
Pick one from each row and learn it properly. The others become familiar in an afternoon.
What it does
Common examples
Work tracking
Holds the list of what needs doing and who is doing it
Jira, Linear, Azure Boards, Trello, GitHub Issues
Version control & hosting
Stores every version of the code and runs code review
Git, plus GitHub, GitLab, Bitbucket or Azure Repos
CI/CD
Builds, tests and deploys automatically when code changes
The tracker is where your work appears and where your progress is visible, so it is worth understanding early.
Jira is the most widely used, and its vocabulary has spread well beyond it. Linear is popular with newer product teams and is faster to use. Azure Boards comes bundled with Microsoft's wider suite. Trello is a simple card board. GitHub Issues keeps tracking next to the code. ServiceNow is a different animal, handling IT service requests and incidents in large enterprises.
The vocabulary you will meet on day one
A ticket, also called an issue, is any unit of work: a feature, a bug, a task, a question.
The assignee is whoever is doing it. The reporter is whoever raised it. These are frequently different people, and confusing them causes a surprising amount of noise.
Workflow status is where the ticket sits: To Do, In Progress, In Review, Done. The exact names vary per team and are usually configurable, which is why they differ everywhere you go.
The backlog is everything not yet scheduled. The sprint is what the team has committed to for the current cycle. Moving something from backlog into a sprint is a decision, not an administrative act.
Linking expresses relationships. "Blocks" and "is blocked by" are the two you will use most, and keeping them accurate is how a team sees what is actually stuck.
You will hear "raise a ticket", meaning create one, and "close the loop", meaning go back and update it so it can be resolved.
Git is the version control system itself. It tracks every change ever made to the code and lets many people work on it at once without overwriting each other.
The verbs you will use constantly: clone to get a copy, branch to start a separate line of work, commit to record a change, push to send it to the shared copy, pull to fetch other people's changes, and merge to combine two lines of work.
GitHub, GitLab, Bitbucket and Azure Repos host Git repositories and add the review step around them. That review step is a pull request on GitHub, and a merge request on GitLab. They are the same idea under two names.
The life of one code change
🌿🌿
BranchStart a separate line of work
1
💾💾
CommitRecord what changed, and why
2
⬆️⬆️
PushShare it with the team
3
👀👀
Pull requestSomeone else reads it
4
🤖🤖
CI checksBuild and tests run automatically
5
🔀🔀
MergeJoins the main line
6
🚀🚀
DeployReaches real users
7
Every change a professional team ships travels this path. The two steps beginners underestimate are the pull request and the automated checks, and those are the two that exist specifically to catch the mistake before a user meets it.
What Do You Think?
Your company uses GitLab, and a job advert you are interested in asks for 'GitHub experience'. How much of a problem is that?
CI/CD tooling watches for new code and reacts. When you push, it builds the project, runs the tests, and often deploys the result. GitHub Actions, GitLab CI, Jenkins and Azure Pipelines all do this. The next lesson but one covers what these pipelines actually do; for now, the useful idea is that "CI is red" means the automated checks failed and something needs your attention before it can merge.
Testing tools run those checks. The names vary enormously by language, and you do not need to know them all. Selenium and Playwright drive a browser like a user would; Postman exercises APIs by hand; JUnit, pytest and Jest run unit tests in Java, Python and JavaScript respectively.
Documentation and design live in Confluence, Notion or a wiki, with interface designs almost always in Figma. Designers will hand you a Figma link and expect you to inspect it for spacing and colours, which is a genuinely useful thing to learn early.
Communication happens in Slack or Teams, with calls in Zoom, Meet or Teams. The unwritten rule worth knowing immediately: decisions made in a call or a direct message do not exist until someone writes them somewhere the rest of the team can find. That is not bureaucracy, it is how distributed teams avoid making the same decision three times.
Quick Check1 / 3
You raised a bug and a colleague is fixing it. In ticket terms, who is the reporter and who is the assignee?
Every company has something for tracking, something for code, something for CI, something for docs, and something for chat. The products vary; the five categories do not.
Assignee and reporter are different people. Workflow status, backlog and sprint are the vocabulary of the board.
Git is the tool; GitHub, GitLab and Bitbucket are hosting plus review around it. Pull request and merge request mean the same thing.
A ticket is communication, not paperwork. What you found matters more than what you did.
Next: A Day and a Sprint in the Life — what the rhythm of the work actually feels like, from stand-up to retrospective, and what the unwritten communication rules are.