Choose a subtopic
Developer tools
Use the everyday tools behind a dependable development workflow. Learn version control, debugging, dependency management, automation and observability.
10 published guides · Free access · Examples & explained answers
10 guides to explore
Git fundamentals: working changes, staging and commits
Git becomes less mysterious when you distinguish the working tree, the staging area and the committed history. A commit records the staged snapshot, not every file you happened to edit.
Read guideGit branches and merge conflicts: combine intent, not just text
A branch lets a line of work move independently in history. When two changes overlap, resolving the conflict means deciding the correct combined behaviour and verifying it afterward.
Read guideCommand-line basics: paths, quoted arguments and pipelines
A command line is an interface for passing arguments to programs. Begin with your current directory, understand which files a command can affect and keep a small practice folder separate from important work.
Read guideBrowser DevTools: inspect the request, layout and actual error
A browser error is not always a JavaScript bug. Use the console, network panel and element inspector to separate a failed request, an incorrect response and a layout problem.
Read guideUse your code editor to navigate, refactor and review deliberately
An editor is more useful when it helps you understand a change, not just type it faster. Combine symbol navigation, targeted search, diagnostics and a final diff review.
Read guideDependency manifests and lockfiles: make installs more repeatable
A dependency manifest describes requested packages; a lockfile records a more precise resolution for a particular ecosystem. Understanding the difference helps explain why two apparently similar installations can behave differently.
Read guideContainers: separate the application image from persistent data
A container packages an application process with a controlled filesystem and runtime environment. Learn what an image provides and which data must survive independently of a particular running container.
Read guideContinuous integration: automate evidence before a release
Continuous integration runs repeatable checks when changes are proposed or combined. Its purpose is useful feedback about a change, not simply a green badge detached from the workflow users depend on.
Read guideTest an API by checking status, headers and body together
A request tool can show what a server actually returned. Use it to investigate a specific contract and keep test requests separate from real customer actions.
Read guideObservability: choose logs, metrics and traces for the question
Operational evidence is easier to use when each signal answers a clear question. Logs record events, metrics summarise measurements and traces help follow work across a request or workflow.
Read guide