Software & Tools overview
73 topics in 14 lessons, each in one line. Every topic opens the page that teaches it.
After this course you can
- Follow a change from source code to a running service, and name every stage it passes through.
- Read and write enough Python, JSON and YAML to automate a task, and keep the work in Git with others.
- Explain how an API, a CLI, Terraform and a CI/CD pipeline each drive a platform, and when to use which.
1How software is built and shipped
- The path to productionOne change passes six stations on its way to users
- LanguagesSomething must turn source code into instructions
- DependenciesMost of what you ship was written by someone else
- The artefactBuild once, and promote the same artefact
- EnvironmentsEach environment answers one question
- Runtime"It works on my machine" is a runtime mismatch
2Programming basics with Python
3Python: data, files and errors
4Data formats
5Version control with Git
6Branching and merging
- BranchesA branch is a movable label, not a copy
- The graphCommitting moves your branch; switching moves HEAD
- Fast-forwardIf main has not moved, a merge just slides the label
- Merge commitsA merge commit joins two histories and has two parents
- ConflictsA conflict is Git asking a question it cannot answer
- Merge or rebaseMerge records what happened; rebase straightens it
- UndoingRewind private work; add a commit to undo shared work
7Working together on GitHub
- RemotesEvery clone is complete; push and pull keep them in step
- PushingA push is refused if the remote has commits you lack
- Pull requestsA pull request is a conversation that ends in a merge
- Branch protectionBranch protection makes the platform enforce the rules
- IssuesAn issue says what and why; a pull request says how
8APIs
- One API callAn API call is one request and one response, in text
- RESTThe URL names a thing; the method says what to do
- Status codesThe first digit of the status says whose move it is
- AuthenticationA token proves who is calling; permissions say what for
- PaginationLong lists come in pages: follow "next" until it ends
9CLIs and SDKs
- Three doorsConsole, CLI and SDK are three doors to one API
- CLI grammarEvery CLI has one grammar: tool, group, action, options
- CredentialsCredentials are found in a fixed order; best is a role
- IdempotencyA script you can safely run twice is one you can trust
- A whole taskA good script: no secrets, every page, safe to rerun
10Infrastructure as code
- DeclarativeYou describe the result; Terraform works out the steps
- Plan and applyplan compares what you want with what exists
- Reading a planRead the plan: -/+ means destroy, then create again
- DriftA change made by hand is drift; apply will undo it
- ModulesA module is a blueprint; variables make each use differ
11CI/CD pipelines
- WorkflowsA workflow is a YAML file: events start jobs of steps
- CI and CDCI proves every change; CD ships the artefact that passed
- SecretsA pipeline holds the keys to production: store none in it
- DeploymentA canary reaches 1% of users before it reaches everyone
- ArtefactsEach job starts clean, so artefacts carry files between
12Testing and code quality
13Debugging and working with AI tools
14One line to productionWorked case
- The changeMost incidents start as a small, reasonable change
- The pathIt passes every gate it meets
- The releaseReleased everywhere at once, a mistake reaches everyone at once
- The causeAn environment variable is always text
- The fixRoll back to the artefact you trust, then ship the fix to a few first
- The trade-offA canary costs minutes and buys a smaller blast radius
- The path, fixedEvery gate catches a different mistake; this one slipped between two
- A real caseAt Knight Capital, one server missed the deployment
Sources and credit
36 sourcesThe chapters and drawings are written by NeuroqAI from these sources. Each lesson lists its own at the end of its chapter, and figures on the pages are taken from them or computed from them.