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.
Containerization is the practice of packaging an application together with all its dependencies — libraries, runtime, system tools, and configuration — into a single, portable unit that can run consistently across any environment. Docker, released in 2013, did not invent this concept, but it standardized the tooling and workflow in a way that made containers…
Git is a system that records changes to files over time, letting you recall any past version. It’s the tool every software team uses to track code, collaborate safely, and undo mistakes. This chapter covers what version control is, why Git became the industry standard, and the properties that make it different from older systems….
Git runs on every major operating system. The installation process differs by platform — Windows uses an installer with many options, Linux uses a package manager, and macOS ships Git with the developer tools. This chapter walks through each, plus verification, so you can confirm Git is ready before you start using it. 1. Installing…
Git works out of the box, but it needs a few settings before you can commit anything meaningful. The most important are your name and email — Git embeds them in every commit as the author. Beyond that, a handful of config options — editor, aliases, default branch — make daily work faster and less…
Git tracks every change to your project with fine-grained control. That control rests on one core idea: a file moves through three states — working directory, staging area, and local repository. Understanding these three states is the foundation of every Git command you’ll ever use. This chapter covers the local workflow — no remotes, no…
Docker presents itself as a single command, but behind that command lies a layered architecture of cooperating processes. The Docker CLI you type into is only the outermost layer, a thin client that translates your input into API calls. Those calls reach the Docker daemon, which handles Docker-specific concerns like networking and volumes before delegating…
A remote repository is a shared, hosted copy of your Git project — the authoritative version that lives on a server instead of your machine. Your local repository holds your work; the remote holds the team’s work. Every push and pull is a conversation between the two. This chapter covers what remote repositories are, why…
A local Git repository works fine on its own — until you want to share it, back it up, or collaborate. That’s when you connect it to a remote. The link is set up once, and after that, push and pull keep the two in sync. This chapter covers the commands that establish that connection…
Linux namespaces are the kernel feature that makes containers possible. A namespace wraps a global system resource in an abstraction that makes it appear to processes within the namespace that they have their own isolated instance of that resource . Changes made by one process inside a namespace are visible to other processes that are…
A branch is an independent line of development. It lets you work on a feature, a fix, or an experiment without touching the stable version of your code. In Git, branches are cheap — creating one is instant, and switching between them is fast. That’s why branching is at the center of almost every Git…