Tooling for Full Stack Developers
Developer tooling is the set of everyday tools that make coding efficient: a terminal for running commands, Git for tracking changes and GitHub for collaborating, and an editor with a debugger. Comfort with these tools matters as much as any framework because every task depends on them.
Stage: Web Fundamentals · Part of the Full Stack Developer roadmap · Last reviewed 19 November 2026
What to learn in Tooling
- Navigate the filesystem and run scripts from the command line
- Commit, branch, merge and resolve a conflict using Git
- Open a pull request on GitHub and respond to review comments
- Set breakpoints and step through code in the editor debugger
- Read stack traces to locate where an error began
Tooling interview questions
Which would you use to update a feature branch, git merge or git rebase?
Merge joins two branches with a merge commit and keeps the original history. Rebase replays your commits on top of another branch, producing a linear history but rewriting commits. Do not rebase commits other people already have. Avoid rebasing commits others already pulled.
How do you debug a Node.js script with breakpoints?
Run it with the inspector, for example node --inspect-brk, or use the editor's built-in debugger configuration. Set breakpoints on lines, run, then inspect variables, the call stack and watch expressions while stepping through the code.
Where Tooling fits in the Full Stack Developer roadmap
Tooling belongs to the Web Fundamentals stage (beginner level), which takes about 5 hours. The shared base for every web developer.
Other units in this stage
Back to the full Full Stack Developer roadmap