Explainers
Short animated explainers on physics, biology, economics, AI and more. Drop in on whatever you are curious about.
41 videosLearn to program
A step-by-step path for complete beginners, from how a computer works to a full-stack app of your own. Start at the first video.
52 videosAutomation QA
For manual testers moving into test automation: learn Playwright step by step, from your first test to CI. Start at the first video.
14 videosDocker and Kubernetes
A step-by-step path from containers to Kubernetes, from why Docker exists to how the control plane works. Start at the first video.
10 videosBehind the scenes
2:03How are web animations turned into videos?
A scene is a function of time: Chromium captures it frame by frame, ffmpeg encodes the video and mixes in the narration.
2:23How does a browser render a page?
From HTML and CSS bytes to pixels: DOM, CSSOM, render tree, layout, paint and compositing.
2:40From typing a URL to seeing the page
DNS, TCP and TLS, a static frontend served from a CDN, one call to a Go API, and the final render.
How AI works
1:14How does AI work?
Neurons and weights, learning from mistakes, and predicting the next word.
1:13How does AI read a sentence?
Tokens, embeddings and attention, stacked in layers to score the next token.
1:17What are billions of parameters?
What a parameter is, how big a billion is, and why big models need racks of GPUs.
1:26How do networks learn from errors?
Loss as a landscape, gradient descent and backpropagation.
1:24How is a chatbot trained?
Pretraining, fine-tuning and human feedback turn a text predictor into an assistant.
1:23What does temperature do?
Scores become probabilities, and temperature sharpens or flattens them.
1:19How does AI draw pictures?
Diffusion models add noise to learn, then remove it to create, steered by a prompt.
1:15How can AI use your own documents?
Retrieval-augmented generation: embed, retrieve, augment the prompt, generate.
1:14Why does AI make things up?
Likely is not the same as true: gaps, snowballing errors, and what helps.
1:16How much can an AI remember?
The context window, forgetting, the cost of long inputs, and workarounds.
1:09What is an AI agent?
A model in a loop with tools and guardrails.
1:12Can AI be biased?
Skewed data, where bias comes from, proxies, and how to audit and fix it.
1:10What is overfitting?
Underfit, good fit and overfit curves, train vs test error, and the fixes.
AI-assisted coding
2:29How to cut Claude Code token usage
A workflow that saves tokens: index the codebase once with graphify and share it with the team, plan from the graph and requirements, confirm the plan, delegate to subagents, then validate.
1:26context-mode: keep tool output out of your context
How the context-mode plugin runs commands in a sandbox so only the answer reaches Claude, indexes large content for search, and restores relevant memory after compaction.
1:16Headroom: compress what the model reads
How Headroom, an open-source context-compression layer, shrinks tool output, logs and code before they reach the model, with content-aware compressors and reversible caching.
Backend runtimes
1:09Why Go?
Why Go exists: single-binary deploys, goroutines scheduled onto a few threads, and channels.
1:16Why Java?
Bytecode and the JVM, the JIT compiler, garbage collection, and why Java suits large systems.
1:12Why Node.js?
Why a single thread with an event loop suits I/O-heavy servers, and where it breaks down.
Why Scrum
1:12Why do we need Scrum?
The problems with plan-everything-first delivery: late feedback, changing requirements and rising cost of change, and how many small bets fix them.
1:17Why Scrum is empirical
Why complex work needs steering by evidence, and how transparency, inspection and adaptation depend on each other.
1:04Why short sprints?
Why timeboxes create fast feedback, smaller risk and protected focus.
1:27Why Scrum roles and events exist
The problem each Scrum accountability and event solves.
1:51Scrum vs Kanban
What the two share, and how they differ in cadence, limits, change, roles and metrics, plus when to choose each.
Money and rates
1:33What is money?
From barter to fiat money: what money does, why it works, and what inflation is.
1:44Money and gold
Why gold was money, how paper receipts and the gold standard worked, why it ended in 1971, and why gold is still stored today.
1:28How exchange rates work
The price of one currency in another: why we need it, what moves it, and who it helps or hurts.
1:31Why US rate hikes shake the world
How a Federal Reserve rate hike pulls money into the dollar and squeezes currencies, debts and growth elsewhere.
2:21Who controls the money supply?
Who decides how much money a country has, and how bank deposits can grow without printing any paper money.
Learn to program
52 videosA step-by-step path for complete beginners: how computers and the web work, then HTML, CSS, JavaScript, Go and a full-stack app of your own.
Start here: Inside a computer →Part 1 · How computers work
1:521Inside a computer
The CPU is the brain, the RAM is the desk and the disk is the filing cabinet: what each part does and how they work together.
2:182On and off: bits and bytes
A bit is one on/off switch, a byte is eight bits, and binary is counting with them. How ASCII turns letters and everything else into 0s and 1s.
1:383What an operating system does
The OS is the manager of the computer: it shares the CPU and RAM between apps, organises files on the disk and talks to your devices.
1:184Your first terminal commands
Talk to the computer by typing: pwd, ls, cd, cat and mkdir, and how to find your way around folders.
Part 2 · How the internet works
1:355Clients and servers
The client asks with a request, the server answers with a response. Like a customer and a kitchen, including what a 404 means.
1:296IP addresses and DNS
Every device has an IP address like a house number, websites have domain names, and DNS is the phone book that turns a name into a number.
1:337From a URL to a page
What happens when you type a URL and press Enter: DNS, a request, a response with HTML, CSS and JavaScript, and the browser building the page.
Part 3 · Think like a programmer
1:278What is a program?
A program is a list of exact instructions the computer follows in order. Algorithm, sequence and bug, explained with a robot that makes a sandwich.
1:079Events: when something happens
An event is something that happens, like a click or a key press, and an event handler is the script that runs when it does. Shown with Scratch blocks.
0:5810Loops: repeat instead of copy
A loop repeats blocks so you do not copy and paste them. Repeat, forever, and drawing shapes with a loop, shown with Scratch blocks.
1:0811Variables: a named box for a value
A variable holds a value under a name, and the value can change. Score, set and change, and what score = score + 1 means.
1:0112Conditions: if and else
A condition is a true or false question. If runs blocks when it is true, else runs when it is false. A fork in the road, with an umbrella or a hat.
1:1013Functions: name a group of blocks
A function is a named group of blocks you define once and call many times. Define, call and parameter, with a draw-a-square function.
1:1314Bugs and debugging
A bug is a mistake in a program. Debugging is finding it and fixing it: predict, run, compare, fix, shown on a square that does not close.
1:3815From Scratch to JavaScript
The same six ideas in blocks and in text: sequence, variable, condition, loop, function and event, plus what syntax and the console are.
Part 4 · HTML and CSS
1:2116What is HTML?
HTML describes the content of a web page with elements: an opening tag, content and a closing tag. The page skeleton, head and body, and nesting.
1:3517Links, images and lists
Attributes add information to a tag: href for links, src and alt for images. How a relative path finds a file, and how ul, ol and li make lists.
1:2218What is CSS?
CSS styles a web page. A rule is a selector, a property and a value, and a link tag joins the style.css file to the HTML page.
1:1319The box model
Every element is a box with four layers: content, padding, border and margin. How each one is set with CSS, and what changes when you change a number.
1:2220DevTools: inspect and fix
Right click and Inspect: the Elements tab, the Styles panel, live edits that vanish on refresh, and the Console for finding errors.
1:1621Classes and ids
A class is a name many elements can share, an id belongs to one element. The dot and hash selectors, and div and span as plain containers.
1:1622Flexbox
Line up elements with display: flex. Flex container and flex items, justify-content, align-items, gap, flex-wrap and flex-direction.
1:1823Responsive design
Make a page fit any screen: the viewport meta tag, flexible sizes with percentages and max-width, and a media query that stacks the cards on narrow screens.
Part 5 · JavaScript in the browser
1:2624What is Git?
Git remembers every saved version of a folder. Repository, commit, and the four first commands: git status, add, commit and log.
1:2425The DOM
The DOM is the tree of nodes the browser builds from your HTML. Find a node with document.querySelector and change it with textContent.
1:1926Events in the browser
An event is something that happens on the page. addEventListener waits for it and runs a handler function, shown next to the same idea in Scratch.
1:1827Changing the page
Toggle a class with classList so CSS restyles an element, and build new elements with createElement and append, like a to-do list adding tasks.
1:1528Arrays and objects
An array is a numbered list, an object is a set of labelled values. An array of objects and a loop turn data into cards.
1:2429Local storage and JSON
localStorage is the browser's notebook for your site. JSON.stringify turns an array or object into text to save, and JSON.parse turns it back.
1:2630Fetch and JSON
The browser is the client and fetch sends the request. The server answers with JSON, async and await wait for it, and the Network tab shows what happened.
1:1631Debugging JavaScript
Find bugs in JavaScript: console.log to look, reading an error message and its line, and a breakpoint to pause and step through code in DevTools.
Part 6 · Go basics
1:3832What is Go?
Go is a compiled language: the compiler turns main.go into a program and checks it before it runs. go run, go build, and the three parts of a first program.
1:2633Variables and types
In Go every variable has a fixed type: int, float64, string or bool. var and :=, why the compiler rejects the wrong type, and zero values.
1:1934If, for and switch
Decisions and loops in Go: if and else without brackets, the three shapes of for (counted, condition, forever), and switch, next to the same ideas in Scratch.
1:2035Slices and maps
A slice is a growing list of one type (append, len, range) and a map connects keys to values (delete, and the comma ok check).
1:1736Structs and methods
A struct groups named, typed fields into your own type, a method is a function that belongs to a type, and a pointer receiver changes the real value instead of a copy.
1:1637Errors in Go
A function that can fail returns an error as a second value. nil means success, and you check it with if err != nil, instead of an error jumping out like in JavaScript.
1:1838Testing in Go
A test is a small program that checks your code. _test.go files, Test functions, go test with PASS and FAIL, and table tests with many cases.
1:2139Packages and modules
A package is a folder of Go files, a module is the whole project (go mod init, go.mod), how import works, and why a capital letter makes a name visible.
Part 7 · Go backend
1:2340How a web server works
A web server waits on a port for requests and sends responses. Handlers, http.HandleFunc and ListenAndServe, and seeing the request in the browser.
1:3041Routes, methods and status codes
A route connects a path and a method to a handler. GET, POST and DELETE, the status codes 200, 201, 400, 404 and 500, and how Go answers 404.
1:1942A JSON API in Go
An API returns data instead of pages. A Go struct becomes JSON with struct tags, a handler writes it with json.NewEncoder, and the page loads it with fetch.
1:2143POST and saving data
A POST request carries data in its body. Decode the JSON into a struct, keep it in a slice (lost on restart), and protect the shared slice with a mutex.
1:1744What is a database?
A database keeps data in tables of rows and columns, like a strict spreadsheet. Primary keys, why data in a file survives a restart, and asking questions with SQL.
1:0145SQL basics
SQL is the language for asking a database: CREATE TABLE, INSERT INTO, SELECT with WHERE and ORDER BY, then UPDATE and DELETE (always with WHERE).
1:1446Go and databases
Go talks to a SQLite database with database/sql and a driver. Exec changes data, Query reads rows into structs, and ? placeholders pass values safely.
1:2047Input, validation and safety
Never trust a request: validate empty and too-long values and answer 400, why ? placeholders stop SQL injection, and keep secrets and database files out of Git.
Part 8 · Full-stack capstone
1:3348How the whole app fits together
A full stack app has a front end, a back end and a database. Follow one click from the page through fetch, the Go server and the database and back, with every term from the earlier lessons.
1:2549Planning a project
Plan before you code: user stories, wireframes on paper, a list of tables and endpoints, and small steps with a done-when for each.
1:1750Staying safe as a developer
Habits that keep you and others safe when you build apps: no secrets in code or Git, made-up test data, never trusting input, crediting other people's work and being kind.
1:2351Deploying an app
From localhost to the home network to the internet: what a server computer, a domain name, DNS and HTTPS do, and why public means more risk.
1:2052What to learn next
A map of next steps after the first year: front-end frameworks and TypeScript, more Go and databases, algorithms, games, security and open source, and how to keep learning safely.
Automation QA with Playwright
14 videosA step-by-step path for manual testers who want to become automation QA: from your first Playwright test to reliable tests running in CI.
Start here: Why automate tests? →Part 1 · From manual to automation
1:531Why automate tests?
What manual regression really costs, what is worth automating and what is not, where Playwright fits in the test pyramid, and why your test cases are the valuable part.
1:382Install Playwright and run your first test
Check Node, create a project with npm init playwright, tour the files it creates, run the example tests and open the HTML report.
1:383Anatomy of a test: from test case to code
Map a manual test case to a Playwright test: the title, the steps as awaited actions, the expected result as an assertion, and how a pass or a failure looks.
Part 2 · Locators, actions, assertions
1:394Locators: find elements like a user
How Playwright finds an element: getByRole, getByLabel, getByText and getByTestId, why long CSS and XPath chains break, and the order to prefer.
1:265Actions: click, fill, check and more
Every verb in a manual test case has a Playwright method: goto, click, fill, check, selectOption, hover, press and setInputFiles, and how Playwright acts like a real user.
1:256Assertions and auto-waiting
Write the expected result with expect, why fixed sleeps make tests slow and flaky, how Playwright waits automatically, and why web-first assertions retry.
Part 3 · Maintainable tests
1:217Structure your tests: describe, hooks, tags
Group tests with describe, share setup in beforeEach, keep every test independent in a fresh browser context, and pick what to run with tags like @smoke.
1:178Page Object Model
Stop repeating locators across tests: put each page's locators and actions in a class, so tests read like manual steps and a UI change is fixed in one place.
1:229Log in once, and use fixtures
Stop logging in through the form in every test: save the session as storage state in a setup project, reuse it in the config, and share helpers with fixtures.
1:2010API testing and mocking the network
Use the request fixture to prepare data through the API, and page.route to fake server responses so you can test empty lists, errors and slow responses.
Part 4 · Debug, fix and run in CI
1:2711Debugging tools: UI mode, codegen, inspector, trace
Find out why a test fails: UI mode with a timeline of snapshots, codegen to draft locators, the inspector to step through, and the trace viewer for failures in CI.
1:2412Flaky tests: find the cause, fix it
What a flaky test is, the usual causes (fixed sleeps, shared data, fragile locators, timing), how to fix each one, and why retries are a safety net, not a cure.
1:2113Reports and running tests in CI
Run Playwright on every pull request with GitHub Actions, run tests in parallel across workers and browsers, and keep the HTML report and traces as artifacts.
1:3314Your automation plan
A practical plan for a manual tester becoming automation QA: start with ten smoke tests, build them well, triage failures as product bug, test bug or environment, and grow each sprint.
Docker and Kubernetes
10 videosA step-by-step path from containers to Kubernetes: why Docker, how container runtimes work, why we orchestrate, then the control plane, etcd, the scheduler and controllers.
Start here: Why Docker? →Containers
1:171Why Docker?
Images, containers, layers, and why containers are lighter than virtual machines.
2:212Why container runtimes?
Docker is one way to run containers, not the only container runtime: the OCI standards, high-level (containerd, CRI-O) vs low-level (runc) runtimes, Podman, and which runtime Kubernetes uses by default.
1:283Why Kubernetes?
Why we orchestrate containers: declarative desired state, scheduling, self-healing, scaling, rolling updates and services.
Kubernetes internals
1:304Inside Kubernetes
The control plane and the nodes: API server, etcd, scheduler, controllers and kubelet, and how a pod gets created.
1:305What does etcd do?
etcd as the Kubernetes database: keys, leader election, Raft quorum, watches and backups.
1:096How the scheduler works
How kube-scheduler picks a node for a pod: filtering, scoring, binding, and how to influence it.
1:217Controllers and reconciliation
The control loop at the heart of Kubernetes: desired vs actual state, Deployments, ReplicaSets and the kubelet.
Deploy and scale
2:258Deployment strategies and zero downtime
Recreate, rolling update, blue-green and canary deployments in Kubernetes, and how readiness probes, maxUnavailable 0, graceful shutdown and PodDisruptionBudgets give zero-downtime releases.
2:349Load balancers, sessions and Redis
How a load balancer spreads traffic, why in-memory sessions and sticky sessions break, how Redis as a shared session store fixes it, and how Services, Ingress and stateless pods fit together in Kubernetes.
2:1610How Kubernetes autoscaling works
The HPA formula and its metrics, requests and scale-down stabilisation, the Vertical Pod Autoscaler, the Cluster Autoscaler and Karpenter for nodes, and KEDA for event-driven scaling.








