Tutorials covering the tools that developers use every day — version control, editors, build systems, package managers, containers, and the command-line utilities that make work faster. Each chapter is standalone, built around real examples and verified commands.
Every repository generates files that should never be committed — build artifacts, dependency folders, editor settings, secrets. .gitignore is how Git is told to look the other way. It’s the file that keeps a repository clean, focused, and safe. Key point: .gitignore only affects untracked files. If a file is already committed, adding it to…
On a shared repository, contributors who have write access can push branches directly. But on most open-source projects, contributors don’t have that access. Forking solves this — you make your own copy of the repository, push changes there, and then ask the original project to pull them in via a pull request. Key point: A…
The package.json file is the single most important file in a Node.js project. It is the manifest that tells npm what the project is, what it depends on, and how to run it. Every npm install, npm run, and npm publish reads this file. The npm documentation describes it as “the whole interface” to npm—without…
Docker Engine does not install the same way on every operating system, and the differences are not cosmetic. On Linux, Docker Engine runs natively as a daemon that talks directly to the kernel’s namespaces and cgroups. On macOS, Docker Engine cannot run natively because macOS is not Linux — it has no namespaces and no…
Good Git habits aren’t about following rules for their own sake — they’re about making history readable, reviewable, and reversible. A clean commit log tells a story. A messy one forces everyone to read diffs. This chapter covers the habits that separate a Git user from a Git practitioner. Key point: The goal of good…
Every package you install with npm lands in one of two places in your package.json: dependencies or devDependencies. The distinction is not cosmetic. It determines whether the package is installed when you build for production, whether it is shipped in your deployment artifact, and whether your production server can actually run the code after deployment….
The Docker CLI is the primary interface for managing containers. Four commands form the core of daily container work: docker run creates and starts a container from an image, docker ps lists containers and their states, docker stop gracefully terminates a running container, and docker rm removes a container from the system. These four operations…
The command line is the foundation of Git, but it isn’t the only way to use it. Git GUIs, IDE integrations, aliases, and hooks turn Git from a tool you type into a tool that works with you — showing history visually, catching mistakes before they happen, automating the repetitive parts. Key point: The command…
Semantic Versioning is a formal specification for how version numbers are assigned and incremented. It exists because version numbers without a shared meaning are useless for dependency management: a consumer cannot look at 2.4.1 and know whether upgrading to 2.5.0 is safe, or whether 3.0.0 will break their code. SemVer solves this by tying each…
A container’s lifecycle is not limited to starting and stopping. Docker provides operations for pausing a running container without terminating it, resuming a paused container, restarting a container with a fresh process, and controlling the signals that govern how a container’s main process terminates. These operations matter because they determine what happens to in-flight work,…