Developer Tools for Backend Developers
Developer tools for backend work are the Linux shell and Git, the two tools used daily. The shell lets you navigate servers, inspect files and processes, and automate tasks with scripts and pipes, while Git records history, enables branches and pull requests, and lets teams merge changes safely.
Stage: Programming and Computer Science Basics · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Developer Tools
- Navigate the file system and search files using ls, find and grep
- Inspect running processes and logs with ps, top and tail -f
- Chain commands with pipes and redirect output to files
- Create branches, commit and merge changes with Git
- Resolve a merge conflict and write a clear commit message
Developer Tools interview questions
What is the difference between git merge and git rebase?
Merge combines two branches by creating a merge commit that preserves history as it happened. Rebase replays your commits on top of another branch, producing a linear history but rewriting commits. Avoid rebasing commits that others have already pulled.
How would you find which process is using a port on Linux?
Use ss -ltnp or lsof -i :PORT to list listening sockets with the owning process id. You can then inspect the process with ps and stop it with kill if appropriate. The commands usually need sudo to show processes owned by other users.
Where Developer Tools fits in the Backend Developer roadmap
Developer Tools belongs to the Programming and Computer Science Basics stage (beginner level), which takes about 4 hours. Pick a language and learn the fundamentals that every backend relies on.
Other units in this stage
Back to the full Backend Developer roadmap