Tutorials covering programming languages, type systems, architecture, tooling, and the patterns used to build software that lasts. Each chapter is standalone, built around real examples and verified facts.
Dart’s type system is built on a small set of core types. The previous chapters covered how variables are declared and how the runtime executes code. This chapter covers the values those variables hold. Dart’s built-in types are not just labels — they are classes with methods, operators, and a defined place in the type…
Namespaces isolate what a container can see. Control groups determine how much of each resource it can use. These two kernel features are complementary and together they form the complete foundation of containerization. Without cgroups, a single container running a runaway process could consume all available memory on the host, saturate every CPU core, or…
Rebasing rewrites commit history by replaying your branch’s commits on top of another branch. Where merge creates a merge commit and preserves both branches, rebase produces a linear history — as if you’d always been working from the latest main. Key point: Rebase rewrites history. That’s its power and its danger. It gives you a…
git stash temporarily saves your uncommitted changes and reverts your working directory to the last commit. It’s the escape hatch for the moment you need to switch tasks but aren’t ready to commit — a half-finished feature, a file you forgot to add, a quick bug that needs attention. Key point: A stash is a…
Cherry-picking applies a specific commit from one branch onto another. Where merge brings an entire branch and rebase replays a range of commits, cherry-pick takes one commit at a time and copies its changes to wherever you are. Key point: Cherry-pick creates a new commit with a new hash. The original stays untouched. This makes…
A tag is a permanent label on a specific commit. Unlike branches, tags don’t move — once placed, they stay on that commit forever. That makes them perfect for marking releases: v1.0, v2.3.1, v1.0.0-rc.2. When someone asks “what code was in version 1.0?”, the tag answers immediately. Key point: A tag is a named pointer…
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…
A repository is the container that holds a project’s files and their complete revision history. Creating one on GitHub is a four-step form: name it, choose who can see it, optionally seed it with starter files, and click create. The visibility choice—public or private—is the only decision that cannot be changed without consequences, and the…
A repository in GitLab is more than a Git directory. It is a project with a default branch, a set of permissions inherited from the namespace hierarchy, and a set of protected branches that enforce who can push and who can merge. The Git commands are the same as anywhere else—git clone, git checkout -b,…