Library
Courses, videos, docs and tutorials from other publishers that we checked and recommend. Every link was opened by a person on the date shown.
How to use this hub: pick a skill, then narrow by cost and format. Start with the shortest item that suits your level, and keep a note of what you would change in your own work. Items marked "free tier" or "paid" say so, and a duration appears only when the publisher states it. Summaries explain why each resource matters to someone who directs AI agents rather than writes every line of code.
879 resources
Skip past the list of resources
ADR community (adr.github.io)
A community-maintained home for architectural decision records: short files that record a decision, the options considered and the reason. It explains the idea, lists templates and links to examples. Read it before you write your first decision record, so you can capture decisions in git in a form that a colleague, or an AI agent, can read later.
AGENTS.md project
The home page of the AGENTS.md convention: one plain file in a repository that tells coding agents how the project works, how to build it and what to avoid. Read it before you write your first agent brief, so your instructions live in git where every agent can find them.
Agile Manifesto
The four values and twelve principles that started the agile movement, on one page. Read it to judge any process an agent or team proposes against the original intent.
Agile Manifesto
The twelve principles behind the manifesto, such as delivering working software frequently and welcoming changing requirements. A short checklist for review of how your team and your agents actually work.
AI Engineer
A long workshop on building agents with the Model Context Protocol, led by an Anthropic engineer. For people who want to see how connections to tools are made.
AI Engineer
Barry Zhang and Mahesh Murag of Anthropic argue for building skills instead of many bespoke agents. It gives a practical view of how agent capabilities may be packaged and governed.
AI Engineer
Barry Zhang of Anthropic on how to build effective agents, at the AI Engineer conference. A compact version of the principles in Anthropic's own guide. Good for forming a clear mental model of agent design.
Andrej Karpathy
Andrej Karpathy shows how he uses LLMs in practice. Concrete usage habits that a product manager can copy.
Anthropic
Introduces the Claude Agent SDK, which lets you build your own agents on the same engine as Claude Code. A manager does not need to code agents, but needs to know what is possible and how an agent loop is built so they can specify one. Read it to judge what your engineers propose.
Anthropic
Describes Agent Skills: folders of instructions and files an agent loads only when needed. It is a clear model of how to give agents your organisation's know-how without bloating every prompt. Read it with the Claude Code skills page.
Anthropic
Anthropic research that tested models in simulated company settings where they could act on their own and sometimes chose harmful actions. It is a sober reminder of why autonomy needs limits, oversight and least privilege. Read it when deciding how much freedom to give an agent.
Anthropic
A free Anthropic Academy course on collaborating with AI effectively, ethically and safely, built around a framework of delegation, description, discernment and diligence. It fits a manager who decides what to hand to AI and how to judge the result. Take it early.
Anthropic
Anthropic's learning site with short courses on using Claude, building with the API and working with Claude Code. Check the catalogue for the current list, because courses are added over time. Use it to get a structured start before you build.
Anthropic
A step-by-step set of notebooks from Anthropic that teaches how to write clear instructions for Claude, with exercises you run yourself. Take it before you start delegating work to AI agents, so you know how to give a precise brief and how to check the answer.
Anthropic
A collection of notebooks and recipes showing effective ways to use Claude, from tool use to evaluations. You do not need to run them all; skim to see what is possible and to give engineers concrete examples to build from.
Anthropic
Ready-to-adapt starter projects for building with Claude, such as a customer support agent and a computer-use demo. Looking at them shows what a real agent project contains. Use them as reference when you review a proposed build.
Anthropic
Anthropic's open repository of five notebook courses: API fundamentals, a prompt engineering tutorial, real-world prompting, prompt evaluations and tool use. Work through the notebooks when you want to run code, not only read about it.
Anthropic
A guide to hooks: small scripts that run automatically at set points in an agent session, for example to block a risky command or run checks after an edit. Hooks are how a manager turns written policy into something an agent cannot skip. Start here, then use the reference page for details.
Anthropic
Practical advice from the makers: give the agent a way to verify its work, explore and plan before coding, keep context clean and write project instructions. The habits apply to any coding agent.
Anthropic
Anthropic's account of running many Claude agents in parallel on one large, well-tested goal, including how tests steered the work. It is one of the clearest public examples of orchestration at scale and of why tests are the manager's lever. Read it to see what a fleet can and cannot do.
Anthropic
An engineering essay on the difference between workflows and agents, and on the simple patterns that work: prompt chaining, routing, parallelisation and evaluator loops. It argues for the simplest design that works. Read it before you give an agent a big job.
Anthropic
Anthropic's talk on how to build more effective AI agents. A 2030 product development manager watches it to learn the design principles behind the agents they will direct and to judge whether an agent design is sound.
Anthropic
Anthropic's free learning hub with courses on using Claude, building with the API, Claude Code and more. It is the official starting place for structured learning on the tools the Dojo teaches. Pick the course that matches where you are on the use, delegate, orchestrate ladder.
Anthropic
A short Anthropic explainer of Agent Skills, reusable packages of instructions for agents. Shows one way to codify your team's know-how for agents.
Anthropic
Anthropic's Code with Claude session on best practices for Claude Code. Watch it to learn how to give an agentic coding tool work and keep it on track.
Anthropic
Shows how to run Claude Code inside GitHub Actions workflows, for example to review pull requests or act on issues. It illustrates agents as a step in a pipeline you already govern. Read it to see how review and automation can combine.
Anthropic
The GitLab counterpart: running Claude Code from GitLab CI/CD jobs and merge requests. Since the Dojo uses GitLab, this is the closest official guide to agents working inside your own pipeline. Read it with the GitLab merge request docs open.
Anthropic
A free Anthropic Academy course on running long, hands-off Claude Code sessions you can trust: steering, configuring, enforcing rules that cannot be skipped, automating and verifying. It matches the use-to-govern ladder closely. Take it alongside the labs in this track. Registration is free.
Anthropic
Anthropic's published statement of the values and priorities it trains Claude to hold. Read it to understand why a model refuses, hedges or pushes back, and why you still own the decision.
Anthropic
Explains letting agents write code to call tools instead of loading every tool into context, saving cost and time. It is a good example of an architecture trade-off a manager should be able to follow. Read it when tool lists get long.
Anthropic
Step-by-step recipes for everyday tasks with Claude Code, such as exploring an unfamiliar codebase, fixing bugs, refactoring, writing tests and creating pull requests. Use it to learn what is reasonable to delegate and how to phrase each request.
Anthropic
Documents letting Claude operate a computer by looking at the screen and clicking. It shows both the reach of agents beyond code and the safety measures they need. Read it to judge proposals that let an agent act in a real interface.
Anthropic
Explains how to allow, ask or deny specific tools and commands for the agent. Permissions are the simplest guardrail you control as a manager: what an agent may do without asking. Read it before you give any agent access to real systems.
Anthropic
Describes running the agent's shell commands inside a sandbox that limits file and network access. It is a practical example of defence in depth for autonomous agents. Read it to ask the right security questions about any agent your team runs.
Anthropic
Explains how to connect Claude Code to external tools and data through the Model Context Protocol. It shows how an agent reaches your issue tracker, docs and services, and why each connection widens what could go wrong. Read it before you grant an agent new tools.
Anthropic
Describes giving an SDK-built agent access to external tools through MCP servers. It helps you scope which tools an agent should have for a given job. Read it when specifying the tool list for a new agent.
Anthropic
Explains what a context window is and how it fills during long work. Many agent failures come from running out of or polluting context, so this is core mental-model material for anyone running long tasks. Read it to understand why briefs should be tight.
Anthropic
Explains how to define specialised subagents with their own instructions and tool access, so one session can hand narrow jobs to focused helpers. This is the first rung of orchestration: splitting work between agents with clear roles. Read it when one agent is no longer enough.
Anthropic
Teaches how to write measurable success criteria and turn them into test cases for an AI system. This is acceptance criteria for AI work, which a Product Development Manager owns. Read it before you accept any agent output as done.
Anthropic
A practical guide to evaluating agents: types of graders, how to build tasks and how to read results. Evals are how you verify agent work at scale, which is the manager's job. Read it before you design your own acceptance tests.
Anthropic
How an organisation can deploy settings and hooks that individual developers cannot override. Read it to see company-level policy enforced as data, and to decide what you would put at that level for a team.
Anthropic
Explains why the information you put in front of a model matters as much as the words of the prompt, and how to keep that context small, relevant and fresh over a long task. Useful when your agent forgets things or drifts.
Anthropic
Describes how to keep an agent productive over many sessions using progress files, feature lists and clean hand-offs. The ideas map directly to how a manager structures long projects for agents. Read it when work spans more than one sitting.
Anthropic
The index of Anthropic's engineering articles on agents, tools, evaluations and Claude Code. Bookmark it: new practical guidance appears here first. Skim it monthly to keep your agent practice current.
Anthropic
The design story behind Agent Skills: packaging procedures and expertise so agents can use them on demand. It frames skills as organisational memory. Read it when you want your team's way of working to travel with the agent.
Anthropic
Shows how to package repeatable instructions and resources as skills that an agent loads when relevant. Skills are reusable delegation briefs for your team's recurring work. Read it when you notice you keep rewriting the same prompt.
Anthropic
Describes letting the model reason step by step before answering and how to budget it. Knowing when deeper reasoning is worth the cost helps you choose settings for hard planning tasks. Read it when quality matters more than speed.
Anthropic
The quickstart for building with the Claude API. A non-coder can read it to see the minimum moving parts of an AI feature: a key, a model, a message. Read it so you can talk to engineers about what an integration really involves.
Anthropic
The full reference for hook events, inputs and decisions in Claude Code. Use it when you need to specify exactly which actions an agent fleet may take and which must be stopped or logged. Pair it with the hooks guide.
Anthropic
Covers the project instruction files and memory that give an agent standing context about your product and rules. Writing these files well is a core manager skill: you state the house rules once instead of in every prompt. Read it when you start a real repository.
Anthropic
A candid engineering account of how Anthropic built a system where a lead agent directs several subagents, including what worked, what failed and how they evaluated it. It is real evidence of the costs and benefits of orchestration. Read it before you propose a multi-agent design.
Anthropic
Shows how to intercept an SDK agent's actions with hooks to approve, block or log them. It is policy-as-code applied to a custom agent. Read it when you need controls in an agent you build yourself.
Anthropic
A long Anthropic conversation on interpretability. For those who want a serious grounding in why models behave as they do and how that bears on trust.
Anthropic
Announces features that help agents discover and call many tools efficiently. Read it to understand how tool-heavy agents are being made practical and what to ask engineers about it.
Anthropic
Anthropic's first public description of its framework for linking model safeguards to capability levels. It is a worked example of governance by written policy with defined triggers. Read it as a model for writing your own policy.
Anthropic
Explains why Anthropic added sandboxing to Claude Code and how it reduces permission prompts while limiting damage. It is a clear case study in trading safety against friction. Read it for the reasoning, then use the docs for set-up.
Anthropic
Explains how Claude Code usage is billed and how to track and limit it. Read it before you run several sessions at once, so budgets are a decision you made and not a surprise.
Anthropic
Shows how to monitor and dispatch several background Claude Code sessions from one screen. It is a practical way to see your sessions at a glance while you run the labs.
Anthropic
A half-hour walk-through of Claude Code from Anthropic. A fast way to see what an agentic coding tool does, so you can judge its output.
Anthropic
Anthropic's research on how much freedom people actually give agents and how that changes with experience. It is a good model of measuring autonomy from evidence instead of from what a team says it does. Read it when you write the scorecard and the autonomy section of your briefing.
Anthropic
Explains layered ways to reduce jailbreaks and prompt injection, including screening inputs and constraining outputs. Prompt injection is the top security risk for agents that read untrusted content. Read it before an agent touches email, web pages or tickets.
Anthropic
Describes the prompt injection risk for agents that browse the web and the defences Anthropic applies. It makes the threat concrete for non-specialists. Read it before you allow any agent to read content you do not control.
Anthropic
Describes how to collect usage and activity data from Claude Code with OpenTelemetry. You cannot manage a fleet of agents you cannot see; this page shows what can be measured. Read it when you start tracking cost and activity per team.
Anthropic
Covers coordinating several Claude Code sessions that work on one goal together. It is a hands-on look at the orchestrate rung of the agent ladder: shared tasks, roles and hand-offs. Read it after you are comfortable delegating to a single agent.
Anthropic
Anthropic describes the principles behind agents that keep humans in control, stay transparent and resist misuse. It supports the idea that humans keep the irreversible decisions. Read it when you decide which decisions stay with a person.
Anthropic
The official introduction to Claude Code, an agentic coding tool that works in your terminal and editor. Read it to see what such a tool can do and how permissions work, before you let one touch a repository.
Anthropic
An overview of bundling commands, agents, hooks and tools into plugins that a whole team can install. It matters for governance because a plugin is how you ship the same guardrails to every session. Read it when you standardise how a team uses agents.
Anthropic
Explains how to reuse repeated prompt content to cut cost and latency. It is useful business-literacy for agent work, where the same long instructions are sent again and again. Read it when you start budgeting agent spend.
Anthropic
The official Claude guide to writing prompts: be clear and direct, give examples, let the model think, use structure and chain steps. Read it before you write your first long prompt and again when an answer disappoints you.
Anthropic
Anthropic's Prompting 101 from Code with Claude. Clear prompts are the core brief you give to agents, so this is foundational for a PDM.
Anthropic
A single page of concrete techniques from Anthropic: be clear and direct, give examples, structure prompts with XML tags, give a role and let the model think. It is the best short reference for writing specifications an agent can follow. Keep it open while you draft briefs.
Anthropic
Practical methods to make a model less likely to state things it does not know, such as allowing it to say it does not know and requiring quotes from sources. Use it to design verification into your workflow instead of hoping for accuracy.
Anthropic
Shows how to run Claude Code from scripts and pipelines without a person at the keyboard. This is how agent work moves from a chat window into automation you can schedule, review and gate. Read it when you want agents inside your CI/CD process.
Anthropic
How to run several Claude Code sessions at once, each in its own git worktree so their files never collide. Use it for the parallel-session lab.
Anthropic
Anthropic's description of how Claude Code is designed to be safe and what risks remain with you. It is a model of the security questions to ask about any coding agent: access, approvals, prompt injection. Read it before rolling agents out to a team.
Anthropic
Shows where Claude Code settings live and which level wins when they conflict (personal, project, organisation). Understanding precedence is the basis of governing many agents with one policy. Read it before you write team-wide rules.
Anthropic
Shows how to make the model return output that follows a schema you define. Structured results are what let one agent hand work to another or to a pipeline reliably. Read it when you design hand-offs between agents.
Anthropic
Explains how to define and use subagents when building with the Agent SDK. It is the programmatic side of delegation: what context each subagent gets and what comes back. Read it after the Claude Code subagents page.
Anthropic
Shows how giving an agent a place to pause and reason improved results on policy-heavy tasks, with measured benchmarks. It is also a lesson in how to test a design idea before adopting it. Read it as a short example of evidence-based agent design.
Anthropic
Anthropic's ongoing research on how people actually use AI across tasks and occupations. For a 2030 manager it is data about which work is being delegated to AI today. Read it to ground your view of the job market in evidence.
Anthropic
Anthropic's talk on the Model Context Protocol, the standard way for AI tools to connect to data and services. It helps you understand how agents get access to your systems, and so what to govern.
Anthropic
Explains how a model calls tools: you define them, the model decides when to use them, your code runs them. Understanding this loop demystifies what an agent is and where control sits. Read it so agent diagrams make sense to you.
Anthropic
Anthropic's rules for what its models may and may not be used for. A product owner building on any AI provider must know the provider's acceptable-use terms. Read it before you design a feature around AI.
Anthropic
A short Anthropic explainer of interpretability, the research on understanding how models work inside. A concise way to understand why verification of AI output matters.
Anthropic
The introduction to MCP, the open standard for connecting AI applications to tools and data. It explains the idea in plain terms: one common plug instead of many custom ones. Read it to follow conversations about how agents get access to your systems.
Anthropic
Shows how to design and test the tools an agent can call, and why evaluation comes before polish. Read it when you start connecting agents to your own systems.
Anthropic (YouTube)
A short video from Anthropic's own channel with practical advice on building and directing AI agents. Watch it before you write your first droid card, then compare its tips with the limits and review points you set.
Aqua Security
The docs for Trivy, a free scanner for images, repositories and configuration files. It shows what a scan reports and how to read a result. Read the overview and the image scanning page.
Argo Project
The official docs for Argo CD, a tool that keeps a Kubernetes cluster equal to what is in git. Start with the overview and the getting started guide. It is reference material to dip into.
Argo Project
Explains automatic sync, pruning and self-heal. These are the settings that make git the only way to change the cluster. Read it to understand what happens when someone edits the cluster by hand.
Atlassian
Practical advice on presenting a roadmap to different audiences. Read it before your 10-minute roadmap review.
Atlassian
An introduction to roadmaps that change as you learn. Use it with the Dojo roadmap standard.
Atlassian
An overview of where AI agents are being used in planning and delivery work. Read it critically, then compare it with the Dojo rule that people write epics and roadmaps.
Atlassian
Explains why a review after an incident should look at process and design, not at a person to blame. It gives a simple structure you can reuse. Read it before you write your first review.
Atlassian
A guide to how teams detect, respond to and learn from incidents. It covers roles such as the incident commander. Use it to compare with the incident loop taught in this program.
Atlassian
Describes ITIL-style change types such as standard, normal and emergency, and why teams classify changes. It uses traditional tools, so translate each idea into a merge request. Read it to understand the words auditors and large companies use.
Atlassian
Explains what a service catalogue is and what an entry usually contains. It is written for classic IT teams, so compare it with a catalogue kept as files in git. Use it to understand why owners and support details matter.
Atlassian
Describes how IT teams capture, store and keep up to date what they know, with a six-stage process and tips for keeping a knowledge base useful. Read it to see how good articles reduce repeat tickets and speed up onboarding.
Atlassian
Explains the difference between an incident and a problem, and how to find root causes. It supports the five-whys habit taught in the incident lessons. Skim the process steps and keep the vocabulary.
Atlassian
Explains what a service request is, how it differs from an incident, a problem and a change, and how request fulfillment works with the service desk. Useful when you design how people ask for access, equipment or information.
Atlassian
Introduces configuration items, their relationships and how a CMDB helps with impact analysis for incidents and changes. It also explains how configuration management differs from IT asset management.
Atlassian
Describes the regular session where a team clarifies, splits and orders upcoming work. A good model for your own weekly pass over the backlog.
Atlassian
A workshop guide to the DACI roles: Driver, Approver, Contributors and Informed. Its main idea is that one named person approves each decision while others advise or are told. Use it to make clear who decides what, and read its claims about success rates as the publisher's own, not as proof.
Atlassian
Atlassian's explanation of epics: large bodies of work broken into smaller stories. Note that Atlassian's meaning of epic is looser than the Dojo's, which crosses several parts of a product. Compare the two and be ready to say how they differ.
Atlassian
Explains how initiatives, epics, stories and tasks nest inside each other. Useful for the four-level picture of vision, epic, milestone and issue taught in the Dojo.
Atlassian
A well-illustrated tutorial series on Git, including comparisons of workflows and when to merge or rebase. Use it for the picture-based explanations.
Atlassian
A short guide to estimating the cost of a project, splitting it into lines and tracking it against the plan. Use it as a checklist for the Budget part of ORBITAL, then ask a finance colleague to check your numbers.
Atlassian
A short play from the Atlassian Team Playbook with preparation steps, questions to ask and how to share what you learn. Run it as written before your first Dojo interview.
Atlassian
A step-by-step guide to a pre-mortem: before a project starts, the team writes down what could go wrong and what must go right, votes on the biggest threats and leaves with actions that each have an owner and a deadline. It is a cheap way to find the questions nobody asked. Use it to draw out hidden assumptions, or to attack a decision before you make it.
Atlassian
A short article that explains the five SMART tests (specific, measurable, achievable, relevant, time-bound) and works through an example. Use it when you rewrite a vague task into one that an agent or a colleague can finish and you can check.
Atlassian
An introduction to IT service management and its practices: requests, incidents, problems, changes and the service catalogue.
Atlassian
A practical guide to objectives and key results (OKRs): what they are, how to write them, how they differ from KPIs and how teams review them. Use it with the Objective and Indicators parts of ORBITAL to check that each objective has numbers that prove it.
Atlassian
A tour of well-known ways to rank work, such as RICE, MoSCoW and value-versus-effort. Read it, then pick one on purpose and explain why it fits your product.
Atlassian
A short team exercise from the Atlassian Team Playbook for agreeing on the problem before anyone argues about solutions. The team answers four questions (who has the problem, what it is, why it matters, where it happens) and then writes one problem statement. Use it to test your own problem statement against a group. The page is clear that the goal is to define the problem, not to solve it.
Atlassian
Explains what a product backlog is, how it differs from a sprint backlog, and how to keep it ordered. Read it before you set up your first board.
Atlassian
An introduction to product discovery: learning what to build and for whom before you build it. It covers the main activities and how discovery continues after launch.
Atlassian
Plain guidance on planning a product launch across teams. Read it next to the go-to-market part of the lesson.
Atlassian
A step-by-step guide to what a product roadmap is, the common formats and the questions it must answer. Read it before you write your own roadmap so you know the standard shapes and can explain why you chose one.
Atlassian
Explains the kinds of dependency between pieces of work and how to track them. Read it before you order your epics.
Atlassian
A one-page template that states a project's goal, the people involved and the risks so everyone shares one picture. A handy format for stakeholder alignment.
Atlassian
Explains who is Responsible, Accountable, Consulted and Informed for each task. A simple tool to share one language across mixed teams.
Atlassian
Explains how a team chooses a sprint goal and the work that fits in the sprint. Read it to see how a goal, a capacity check and a short list of tasks fit together.
Atlassian
Explains the short daily check-in and what makes one useful. Adapt the three questions to a one-person product team that steers agents.
Atlassian
A quarterly team check-up from the Atlassian Team Playbook that rates a team against eight traits, such as shared understanding, ways of working and continuous improvement, and then picks three to work on. Use it as a model for a regular review of how your whole team is working, including the agents' part of the work.
Atlassian
Shows how to write a user story, with a template and examples, and how stories sit under epics. Use it to learn the standard 'as a, I want, so that' form and its limits.
Atlassian
Describes how a team looks back at its last stretch of work and agrees what to change. A practical guide for running your own weekly review, alone or with agents in the loop.
Atlassian
Explains story points, relative estimation and common methods such as planning poker. Read it to understand what estimates are for, and why they are rough on purpose.
Atlassian
An Atlassian Agile Coach video on the product manager role and why it is debated. Useful for understanding the job the Dojo is training you towards.
Atlassian
Explains the MVP idea: the smallest version that lets you learn from real customers. Use it to sharpen what goes in your first version and what you leave out.
Atlassian
Explains what goes in a short product brief and shows an example. A good companion to the Dojo product brief template.
Atlassian
Describes the product owner role that sits closest to the PDM role. Use it to compare what is the same and what the PDM adds.
Atlassian
Explains the end-of-sprint session where a team shows what it built and gathers feedback. A good template for your own demo to stakeholders.
Atlassian
Atlassian's plain-language home for its Agile Coach material. It explains the Agile idea, how it differs from older plan-everything-first methods, and links to short guides on Scrum, Kanban and backlogs. Start here if the word Agile still feels like jargon.
Atlassian
A short Atlassian video introducing Agile in plain words. A quick way to get the main idea before reading the longer guides.
Atlassian
Describes continuous integration and delivery, the pipeline idea that sits under Launch Sequence. A gentle first read before the GitLab pipeline docs.
Atlassian
Explains the checklist a piece of work must pass before a team starts it. Apply the same idea to decide when a milestone is ready to hand to an agent.
Atlassian
Explains DevOps as a way for development and operations to work together, with the usual practices (continuous delivery, monitoring, feedback). Good for seeing the loop that ANDROID Ops keeps.
Atlassian
Explains Kanban boards, work-in-progress limits and continuous flow. Useful when your work arrives as a stream of small tasks (as agent work often does) instead of in fixed-length sprints.
Atlassian
A friendly overview of Scrum: the roles, the sprint, the backlog and the meetings, with diagrams. It is easier to read than the official guide and a good first pass before you read the Scrum Guide itself.
Atlassian
Shows how to lay out a user's journey across the top and the work under each step. It is a bridge between journey maps and a backlog, which is exactly the move you make between Dojo weeks 2 and 3.
Atlassian
Explains a shared checklist that says when work is truly finished. It is the human version of the acceptance checks you give an AI agent.
Atlassian
A step-by-step workshop from the Atlassian Team Playbook for agreeing, in writing, how a team works together: how it communicates, when it meets and how it decides. It comes with free templates. Use it to turn unspoken expectations into a short page the whole team, and any agent working with it, can read.
AWS
A hands-on workshop for Kubernetes on AWS. Labs may create billable resources.
AWS
AWS's free programme for learning cloud skills. Check the page for current eligibility.
AWS
AWS's description of its free offers. Read the current terms and limits carefully before you create an account, because they change.
AWS
AWS's guide to monitoring and observability patterns, with open-source and AWS-native options.
AWS
AWS's learning centre with free digital training and an optional paid subscription for extras. Start with its free cloud fundamentals material.
AWS
AWS's framework of design questions grouped by pillars such as security, reliability, cost and operations. Even if you do not use AWS, the questions are a good review checklist.
AWS
AWS's framework of six pillars for reviewing cloud workloads: operational excellence, security, reliability, performance, cost and sustainability. A manager's checklist for architecture reviews even when you do not use AWS.
AWS
Hands-on labs for the Well-Architected pillars. Practise on a real account to see a review turn into changes. Labs may create billable resources, so watch costs.
AWS
Articles by Amazon engineers on how Amazon builds and operates systems, covering reliability, deployment and architecture. They are written for decision makers as well as engineers.
AWS
AWS's entry page with hands-on tutorials and guided paths for first steps. Choose a tutorial that matches your task and watch for charges, then delete what you create.
AWS
AWS's best practices for Kubernetes. Useful for security and reliability checklists.
AWS
Explains AWS Budgets, which track spending and send alerts when it passes a limit you set. Set one before any hands-on work.
AWS
The operational excellence pillar: running and monitoring systems and improving continually. A short guide to operating what you ship.
AWS
The overview of Amazon Bedrock, AWS's service for using foundation models. It shows how a cloud provider offers many models behind one interface.
AWS
A whitepaper that tours the AWS service categories in plain language. Use it to learn what services exist and what they are called.
AWS
The reliability pillar: failure management, change management and workload design. Helps you ask how a product recovers.
AWS
AWS's checklist for identity and access: protect the root account, use temporary credentials, grant least privilege and turn on multi-factor sign-in. Read it before you let any person or agent hold AWS access.
AWS
The security pillar of AWS's framework: identity, detection, protection and response. A solid structure for cloud security review.
AWS
AWS's introduction to object storage: buckets, objects and keys. It defines the S3 model that SeaweedFS and many other stores copy.
AWS
A plain overview of DevOps culture and practices. A concise introduction.
AWS
A plain explanation of MLOps, why models need operations too, and how teams organise the work. Useful for the part of ANDROID Ops that covers AI features.
Axelos
The owner's overview of ITIL, the best-known framework for IT service management. Read it to learn what the framework is called and what it covers. Certification is paid, but this page is free to read.
Backstage
Explains how a catalogue of services can be kept as files in the same repositories as the code. This is the same idea as catalogue entries in git. Read the overview to see what an entry holds.
Backstage
An overview of a popular open source developer portal. Read it to judge the product fairly before you decide whether you need one. It explains the catalogue idea at the core.
Brown University Library
A page in a university data management tutorial. It recommends a research notebook that records design decisions and methods, and README files that explain how files were made. The same habits apply to an evidence log in git: write down what you did so someone else can repeat it.
Bun
Short, task-based guides from the Bun team: build an HTTP server, read files, connect to a database, write tests. Pick the one that matches the job in front of you.
Bun
How Bun's built-in test runner works, how to run and filter tests, and how to read results. Useful when you need to judge whether the tests an agent added really prove anything.
Bun
The official Bun documentation: the runtime, package manager, test runner and bundler in one toolkit. Use it to look up any command an agent runs in a PHANTOMS repository.
Bun
Explains how one repository holds several packages that share one lockfile. This is the base layer under the PHANTOMS apps and packages folders.
Charm
The official step-by-step tutorial for Bubble Tea, a Go framework for terminal apps built on a model, an update step and a view. Read it so you can follow how a terminal app keeps state.
Charm
Bubbles is the library of ready-made terminal components for Bubble Tea, such as lists, tables, spinners and text inputs. Read it to learn what you can ask an agent to reuse instead of rebuilding.
Charm
The Bubble Tea repository: README, examples and releases. Check it for the current API before you accept an agent's terminal UI code.
Charm
Huh builds forms and prompts for the terminal, such as selects, confirms and text inputs. It is the part of the Charm family that collects structured input from a user.
Charm
Lip Gloss is the Charm library for styling terminal output: colours, borders, padding and layout. Look here to see how a terminal app gets its brand look.
CISA
The U.S. cyber agency's guidance asking software makers to take ownership of customer security outcomes. It shows the direction of the industry.
CISA
The U.S. Cybersecurity and Infrastructure Security Agency's plain explanation of what an SBOM is and why governments and buyers ask for one. A good first read if you need to explain SBOMs to a non-technical stakeholder.
Claude
A short video on how Claude Code works. Understanding the loop of an agent helps you set realistic expectations and review its work.
Claude
A talk on how a team uses Claude Code in its own work. A real example of agent-assisted development you can learn working habits from.
Claude
A short Claude video on skills. Pairs with the Agent Skills explainer to show how to teach agents repeatable procedures.
Claude
A short video introducing Claude Code. A quick orientation for anyone who will delegate work to it.
Cloud Native Computing Foundation
A searchable map of open source cloud tools grouped by job. Use it for the search step of the open-source-first ladder. Filter by category and licence.
CNCF
Plain-language definitions of cloud-native terms. It is useful to keep open in design reviews.
CNCF
A CNCF paper on internal platforms and why they exist. It gives product-minded language for treating a platform as a product with users.
CNCF
The OpenTelemetry documentation. The open standard for traces, metrics and logs; it is the common language of observability.
CNCF
The getting-started guide for Flux, a GitOps tool. Compare it with Argo CD to separate the principle from the product.
CNCF
A hands-on first run of Prometheus. Shows how metrics are collected and queried.
CNCF
The Argo CD getting-started guide. Walk through it once to see a git change appear in a cluster.
CNCF
The introduction to Kyverno, a policy engine for Kubernetes. A second view of policy as code beside Open Policy Agent.
CNCF
The CNCF security community's whitepaper on cloud-native security across the lifecycle. A thorough framework for security conversations.
CNCF
The docs for Falco, runtime security detection for cloud-native systems. Read the intro for the idea of watching what running workloads actually do.
CNCF
The Crossplane documentation: managing cloud infrastructure through Kubernetes-style APIs. It shows the platform-as-product idea.
CNCF [Cloud Native Computing Foundation]
A short CNCF video on delivering GitOps with Argo CD. Shows the idea of git as the source of truth for deployments.
CNCF [Cloud Native Computing Foundation]
A CNCF talk introducing Argo CD. Walks through what a GitOps controller does.
CNCF [Cloud Native Computing Foundation]
A five-minute lightning talk on OpenTelemetry. A quick view of the standard for observability.
CNCF [Cloud Native Computing Foundation]
A CNCF talk by Camille Fournier and Ian Nowland on starting and scaling a platform engineering team. Useful for a manager deciding how to organise shared platforms.
CNCF [Cloud Native Computing Foundation]
The CNCF's illustrated guide to Kubernetes as a story. A friendly way to explain Kubernetes to non-engineers.
Cognitect
The short blog post that made decision records popular. It argues for one short document per decision with context, decision and consequences. A five-minute read.
Consortium for Service Innovation
The free library for the Knowledge-Centered Success method, with the principles, core concepts and practices guide for capturing knowledge while solving problems. The library is free for personal use with attribution; training and certification are separate and are not free.
Continuous Delivery
A clear definition of continuous delivery with the principles behind it, from the authors of the book of the same name. Short and worth reading early.
Conventional Commits
A small specification for commit messages with a type, an optional scope and a description. It makes history readable by people and tools. You may adopt it fully or just borrow the habit.
Cornell University Library
A library tutorial on judging what you find. It starts with general questions for any source, then covers scholarly literature types, primary and secondary articles, peer review, systematic reviews, grey literature and how to read science news. Use it to learn what kind of source an agent has handed you.
Crossref
Crossref's documentation for its open API, which returns metadata about published works as JSON. No sign-up is needed. You can look up a work by its DOI and compare the title, authors and year with what an agent claimed. It is the fastest way to catch an invented citation. A DOI that Crossref does not know may still exist elsewhere, so treat a miss as a reason to look further, not as proof.
Curiosity Research Corporation
The public PHANTOMS core starter: a runnable Bun, PostgreSQL, Hono and Next.js app with an AGENTS.md file and guides for setup, security and CI. Clone it to follow the Dojo track, and read its docs to see how a repository can brief an AI agent.
CycloneDX
Home of one of the two common formats for a software bill of materials (SBOM), the list of parts inside a product. Use it to see what an SBOM file looks like and which tools produce one.
DeepLearning.AI
A short course on building systems where several agents cooperate: reflection, tool use, planning and multi-agent chat. Take it after you have used a single coding agent for a while and want to see how teams of agents work.
DeepLearning.AI
A free short course on building agents as controllable graphs with persistence and human-in-the-loop steps. It shows how to put a person into an agent workflow. Take it when you want to see approvals designed in.
DeepLearning.AI
A beginner Python course that uses an AI assistant while you learn. It shows how to read and fix code that an assistant writes for you. Good for career changers who need to read code before they can review it.
DeepLearning.AI
A free short course on putting automated evaluations into a CI pipeline for AI applications. It is a direct example of gates for AI work. Take it to see tests running on every change.
DeepLearning.AI
A short free course on agents that retrieve and reason over documents. RAG is the standard way to ground AI in your own knowledge, so you will meet it often. Take it for the concept.
DeepLearning.AI
A free short course on chaining prompts, classifying inputs, checking outputs and evaluating a multi-step system. It teaches the shape of an AI workflow, which is the base for orchestrating agents.
DeepLearning.AI
A free short course on how multimodal models and tools lead up to agents that use a computer. It explains the building blocks and their risks.
DeepLearning.AI
A short course, taught with OpenAI, on writing prompts in code: clear instructions, iterating, summarising, inferring, transforming and expanding text. It is quick and hands-on. The API details change, the habits do not.
DeepLearning.AI
A free short course by Anthropic's Elie Schoppik on exploring, building, testing and refactoring with Claude Code, including running several instances at once. It shows agent delegation in practice. Take it before your first real project.
DeepLearning.AI
Short, free video courses on working with language models and agents. Pick one that matches the tools you use. Check each course page, as a few may change over time.
DeepLearning.AI
A short course on how to measure whether an agent does its job, including tracing each step it takes and scoring the results. Take it when you want to move from 'it looks right' to 'we tested it'.
DeepLearning.AI
A free short course on how models call functions and extract structured data. It is a compact way to see the tool-use loop working.
DeepLearning.AI
A free short course on building a chatbot over your own documents. It illustrates the retrieval pattern behind many internal AI assistants.
DeepLearning.AI
A free short course on automating the pipeline for building, testing and running language-model applications. It links CI/CD ideas to AI products. Take it if you will run AI features in production.
DeepLearning.AI
A free short course on how agents manage memory beyond one conversation. Memory shapes how agents behave across sessions and what they may reveal.
DeepLearning.AI
A free short course taught with Anthropic on building and connecting MCP servers and clients. It deepens the picture of how agents reach tools and data.
DeepLearning.AI
A free short course on assigning roles, goals and tasks to a crew of agents for business workflows. It maps well to how a manager thinks about a team. Take it to practise decomposing a process.
DeepLearning.AI
A free short course on validating and structuring model outputs. Validation is a gate between agent steps. Take it for the idea of checking data before it moves on.
DeepLearning.AI
A free short course on finding weaknesses in AI applications by attacking them. It teaches the mindset and basic techniques. Take it before your first launch of an AI feature.
DeepLearning.AI
DeepLearning.AI's weekly AI newsletter and archive, with Andrew Ng's letters. It is a low-effort way to keep up with the field. Subscribe or skim the archive for trends.
DeepLearningAI
Andrew Ng's AI for Everyone, an introduction to AI for non-technical people. Shared vocabulary for working with AI teams and agents.
DeepLearningAI
A short course with Andrew Ng on building an app with AI help. It shows what a non-engineer can now build.
DeepLearningAI
A full prompting course with Andrew Ng on the DeepLearning.AI channel. A good structured way to learn how to get reliable results from models.
DeepLearningAI
A short DeepLearning.AI introduction to building agentic AI systems with Andrew Ng. Shows why agent workflows can beat a single prompt.
DeepLearningAI
A short DeepLearning.AI video on equipping agents with reusable skills. A companion to the Anthropic skills material.
DefectDojo
Docs for a free tool that collects security findings from many scanners in one place. Read the introduction to understand why one findings tracker helps. It is reference material.
Digital Inquiry Group
Free lessons and assessments, written for teachers, on how to judge information you find online. The method asks three questions: who is behind it, what is the evidence, and what do other sources say. Start with the lessons on lateral reading and on what the evidence is, and use them on every statistic you want to quote and on every AI answer.
Digital.gov
Practical guidance from the US government for writing clearly: know your reader, use short words, keep sentences short. It is ideal for writing for readers whose first language is not English. Read the guidelines page.
Docker
Explains BuildKit, the modern engine that builds container images, with caching and secrets handling. Read it when you need faster or safer image builds.
Docker
Docker's official quickstart for running a small multi-service app with one compose file. It explains the same idea PHANTOMS uses to start a local PostgreSQL database with one command.
Docker
Docker's own introduction to containers and images, with a hands-on workshop. You need to understand images before you can understand pipelines that build them.
Donella Meadows Project
A collection of resources on systems thinking from the Donella Meadows Project. A 2030 PDM manages whole systems of people, agents and customers, and this is a good doorway into that way of thinking.
Donella Meadows Project
The archive of Meadows's writings on systems, sustainability and change. Browse for rigorous systems thinking.
DORA
The research programme behind the well-known delivery metrics, with guides and capabilities that help a team improve. Use it to see delivery as a set of habits you can measure and improve.
DORA
The guide that defines the delivery metrics and warns against using them to compare or rank people. Read it before you put numbers on a dashboard.
Drizzle Team
The overview of Drizzle ORM, the SQL-first TypeScript library the PHANTOMS starter uses for its database package. Read it to understand schema files and migrations before you review an agent's database change.
European Union
A plain summary of the EU AI Act and its risk tiers. If your product might reach European users, you need to know which tier applies. This is a good first read, not legal advice.
European Union
An independent site with the text and analysis of the EU AI Act. Use it to look up articles and annexes referenced in summaries.
Eurostat
The European Union statistics office explains NACE, the classification of economic activities used across the EU, and links to the current version and its tables. Use it to find the European code for your industry, so your galaxy page can be read by partners and funders in Europe.
External Secrets
Documents a Kubernetes add-on that reads secrets from a vault and creates cluster secrets, so git holds only the names. It is the practical form of the rule that secret names go in git but values do not. Read the introduction.
Farnam Street
A podcast conversation on the psychology behind decisions. Useful for understanding why customers and stakeholders choose as they do.
Farnam Street
Explains solving problems by asking what to avoid. It is also a natural method for risk reviews and pre-mortems.
Farnam Street
Explains knowing the edge of what you really understand. Essential when you must judge agent output in areas you do not know deeply.
Farnam Street
A guide to around a hundred mental models for decision making. A PDM makes many judgment calls; this is a toolkit for making them deliberately.
Farnam Street
Explains thinking beyond the immediate effect of a decision. Useful when you weigh a roadmap choice or decide how much to delegate to agents.
Farnam Street
Explains breaking a problem down to fundamentals and rebuilding. Helpful for challenging inherited assumptions in a product.
Figma
A collection of Figma guides on brand storytelling and frameworks. Read it for ideas on how to say what your product stands for.
Figma
Figma's guide to colour basics: the wheel, harmony, contrast and meaning. Use it when you choose your two brand colours.
Figma
Frameworks for comparing your product with alternatives. Use them to structure the competitor part of discovery.
Figma
The first video in Figma's own beginner course, which walks through designing a personal portfolio website. Start the series if you have never used Figma.
Figma
Figma's guides to design research methods and templates. Useful for ideas on how to plan, run and write up customer research.
Figma
Figma's official help-centre section for new users: the interface, frames, layers and sharing. Check Figma's plans page for current pricing and what each plan includes.
Figma
Figma's collection of guides to wireframes and prototypes: what each is, when to use it and how to make one. Good background for your mockup exercise.
Figma
Figma's guide to typefaces, hierarchy and pairing fonts. Use it when you choose your brand font.
Figma
An overview of web design basics: layout, navigation, responsive design and tools. A good checklist before you plan a product site.
FinOps Foundation
The FinOps Framework describes how teams inform, optimise and operate cloud spending together. Use it to build the cost view for Mission Control.
FinOps Foundation
An introduction to FinOps, the practice of making cloud cost visible and managed by engineers, finance and the business together.
Flux project
The documentation of Flux, another CNCF GitOps tool. Read it beside Argo CD to see that the idea matters more than the tool.
Free Software Foundation Europe
A simple standard for marking the licence and copyright of every file in a repository. It shows good practice for your own patch sets and forks. Read the tutorial page.
freeCodeCamp
freeCodeCamp's free back-end curriculum. Literacy in how services and APIs work.
freeCodeCamp
A beginner tutorial on Git and GitHub. Read for the model of commits and branches.
freeCodeCamp
freeCodeCamp's free information security curriculum with projects. A guided, hands-on route.
freeCodeCamp
freeCodeCamp's main learning page, a large set of free interactive courses. Pick a path for literacy.
freeCodeCamp
freeCodeCamp's free machine learning curriculum with projects. Take it for hands-on understanding.
freeCodeCamp
freeCodeCamp's free curriculum on testing. Tests are how you verify agent work.
freeCodeCamp
A beginner's guide to technical writing. Useful for writing documentation and briefs.
freeCodeCamp
A free handbook on Docker. Containers are the unit of deployment; understand them.
freeCodeCamp
A free handbook on Kubernetes. A gentle introduction in writing.
freeCodeCamp.org
freeCodeCamp's AWS Cloud Practitioner course. Free cloud fundamentals; the exam itself is paid and optional.
freeCodeCamp.org
freeCodeCamp's Docker tutorial for beginners. Containers are the unit that agents and pipelines ship.
freeCodeCamp.org
A freeCodeCamp course on designing websites in Figma, from the tool basics to a full design. Good if you want to draw your own mockups.
freeCodeCamp.org
A freeCodeCamp course on designing a real mobile app in Figma while using user research and the design thinking process. Long, so use it as a reference.
freeCodeCamp.org
freeCodeCamp's beginner Kubernetes course. A long, hands-on option.
freeCodeCamp.org
freeCodeCamp's full beginner course on Git. A longer, structured option for understanding version control.
freeCodeCamp.org
freeCodeCamp's full beginner course on HTML and CSS. Literacy in what a website is made of.
freeCodeCamp.org
freeCodeCamp's full Azure Fundamentals course, aimed at the AZ-900 exam. A free way to learn cloud basics even if you skip the exam.
freeCodeCamp.org
A freeCodeCamp course on product management for app builders, from turning a solution into reality. It is long, so pick the chapters that match your current week.
freeCodeCamp.org (YouTube)
A long video course from the freeCodeCamp.org channel that walks through installing PostgreSQL and writing SQL from scratch. Watch it if you prefer to see the commands run before you read the manual.
Git SCM
The free, full book on Git. Read the first three chapters on basics and branching. Use the rest as a reference.
GitHub
GitHub's code owners feature. The concept of naming required reviewers per path is the same across platforms.
GitHub
GitHub's explanation of protected branch rules. Compare it with GitLab's protected branches to see the common idea of a gate on main.
GitHub
Explains rulesets that apply branch and tag rules across a repository or organisation. A model for centrally governing many repositories.
GitHub
A guide for people who run projects, including how to write things down, set expectations and say no kindly. These are the same habits you need when many people ask you for many things.
GitHub
A plain summary of common open source licences with what each lets you do. It is a quick way to learn the families in the licence table. It is not legal advice, so read the real licence file.
GitHub
The official reference manual for every Git command. Use it to check exactly what a command an agent ran will do.
GitHub
Short guides on common Git tasks such as commit, branch, push and pull. They are the quickest way to refresh the commands you will see in agent logs.
GitHub
The documentation for GitHub Actions workflows. Learning one CI system makes the others easy, and the concepts transfer to GitLab CI.
GitHub
The official GitHub documentation for Copilot, covering chat, code suggestions and agent features. Read the sections on how to review its output and what data it uses. Some features need a paid plan, so check which plan you have.
GitHub
The official GitHub documentation. Even if you use GitLab, much of the world's open source lives on GitHub, so you should know how to read these docs.
GitHub
GitHub's free interactive courses where you learn by completing tasks in a real repository, including Git, pull requests and Actions. A good hands-on route to learn how change review works. The ideas transfer to GitLab.
GitHub
Explains how to host a static site from a repository. Handy for publishing a product website at no cost.
GitHub
An open-source toolkit for spec-driven development: you write the specification and agents build to it. It is a close match to the Dojo's idea that people specify and agents build. Read the README to see one way the workflow can run.
GitHub
A ten-minute walk-through of repositories, branches, commits and pull requests. It is the shortest way to understand the change review cycle that all agent work flows through.
GitHub
Explains governance in open source projects, roles and decision making. It gives you practical models for how decisions are made when no one reports to you.
GitHub
GitHub's merge queue, the equivalent of GitLab merge trains. Reading both shows the same idea twice.
GitHub
A set of free guides on using, contributing to and running open source projects. Start with the legal and contribution guides. It gives the culture behind the open-source-first habit.
GitHub
Walks through how to send a first contribution to someone else's project. It is useful for the step of sending a change upstream before keeping a patch. Read it before you open an upstream pull request.
GitHub
Explains in plain language why licences matter and what happens when code has none. It supports the rule that code with no licence file is not open source. A short, readable guide.
GitHub
Explains which measures show the health of a project and how to use them. A good small lesson in choosing metrics that inform decisions.
GitHub
The documentation for pull requests, GitHub's equivalent of merge requests. Read it to compare how two platforms handle review.
GitHub
GitHub's guidance on securing Actions workflows, including secrets, third-party actions and permissions. The lessons apply to any pipeline.
GitHub
Documents GitHub's security features such as secret scanning and dependency alerts. Read it to know what automated checks are available.
GitHub
Explains how to launch an open source project: why, naming, licensing and launching. Useful for anyone planning to open their own work.
GitHub
GitHub's introduction to workflows, jobs, steps and runners. The concepts map directly to other CI systems, so read it even if you use GitLab.
GitLab
How one company runs the regular one-to-one meeting between a manager and a team member: a shared written agenda, mostly the other person's topics, a steady rhythm and feedback given right away instead of saved for the meeting. Use it to design your own one-to-one, and adapt it to your size and time zones.
GitLab
Overview of the scanners GitLab can run in a pipeline. Check which scanners are in your plan, because some features are paid.
GitLab
How GitLab records who did what. This is the platform side of the governance stage. Availability depends on plan.
GitLab
Shows the single place to see protection, approvals and required checks for each branch. It gives you one view of the rules that gate change.
GitLab
A public page on how leaders can build trust, with three ingredients (empathy, respect and selflessness) and practical habits for remote teams. It is a useful partner to feedback skills, because feedback is easier to hear where trust already exists. It is one company's view, so choose the habits that fit your team.
GitLab
Shows how to keep downloaded dependencies between jobs so pipelines run faster, and how caches differ from artifacts.
GitLab
Explains copying a single commit to another branch. A handy technique for fixes that need to land in more than one place.
GitLab
Describes reusable pipeline building blocks that you can share across projects. This is the basis of a standard pipeline template.
GitLab
A collection of example pipelines for common languages and tasks. Use it to see what a normal pipeline looks like so you can spot an odd one.
GitLab
How pipelines, stages and jobs fit together in GitLab. The base reference for turning a checklist into automatic gates.
GitLab
Explains how to pass settings and secrets to jobs, including masked and protected variables. Read the security notes before you store any token.
GitLab
The full reference for every keyword in a .gitlab-ci.yml file. You will not read it end to end. Search it whenever a keyword is unclear.
GitLab
Explains AI code suggestions in GitLab. Check the page for plan availability. Read it to know what a developer sees when an assistant is on.
GitLab
A cheat sheet of everyday Git commands from GitLab's docs. Print it or keep it open in your first month.
GitLab
Describes labelling projects with compliance requirements and enforcing controls. It shows policy tied to projects. Check the page for plan availability.
GitLab
Explains GitLab's agent for connecting Kubernetes clusters and GitOps style delivery. Read it to see how a repository and a cluster stay in sync.
GitLab
Explains scanning of the libraries your project uses for known vulnerabilities. Check plan availability.
GitLab
Explains how to store issue and merge request templates in your repository so each new item starts with the right headings. Use it to ship your epic template with the project.
GitLab
Explains environments and deployments in GitLab: how a pipeline records where each version runs. Read it when you add a staging or production stage.
GitLab
GitLab's documentation for epics, which group related issues across projects. Check the page for which GitLab tier includes the feature before you rely on it. On the free plan, use labelled issues instead.
GitLab
A GitLab video on epics and issue boards. Shows how to structure work from epic to issue.
GitLab
Explains feature flags for turning features on and off without redeploying. Flags let you release safely and learn from users. Check the page for plan availability.
GitLab
GitLab's short overview of agile project management in GitLab. Shows issues, boards and iterations together.
GitLab
Documents glab, the GitLab command-line tool. Agents use command-line tools like this to open issues and merge requests, so reading it shows what an agent can do on your behalf.
GitLab
How a large remote company communicates: write things down, work in public by default and keep a single source of truth. A real, public example of the habits taught in the Dojo.
GitLab
Explains GitLab's built-in registry for container images. It is where build output is stored before deployment. Read it to follow how an image moves from build to run.
GitLab
The official GitLab documentation, the first place to look when you are unsure how a feature works. Learning to navigate it is a core skill because agents and teammates will both ask you to check what GitLab really supports. Bookmark it.
GitLab
Describes the CODEOWNERS file, which names the people or groups who must review changes to given paths. Use it to record who owns what, in git, next to the code. Pair it with approval rules for sensitive files.
GitLab
An entry point to pipelines, jobs and runners. It shows how a .gitlab-ci.yml file turns a commit into tests, scans and a build. Read the getting-started section before you design a pipeline gate.
GitLab
Step-by-step instructions for creating an epic, editing it, adding child epics and linking issues. Use it as the practical companion when you move your hand-written epics into GitLab. It is reference material, so scan the headings and read only the steps you need.
GitLab
Documents GitLab's AI features. Check the page for plan availability. Read it to see how AI assistance is built into the same merge requests and pipelines you already govern.
GitLab
GitLab explains its Duo Agent Platform. Shows how AI agents are being built into the same issues and merge requests you manage.
GitLab
GitLab's short video explaining a first CI/CD pipeline. A fast orientation for people who have never read one.
GitLab
Explains how GitLab Pages publishes a static website straight from a repository. A free way to host a product website with its source in git.
GitLab
Free self-paced courses from GitLab on planning, source control and CI/CD. Pick the short beginner paths that match your week, not the whole catalogue. Some certificates may cost money; the learning material itself is free to follow.
GitLab
Explains how GitLab can store and lock state for you, so the state file does not sit on a laptop.
GitLab
GitLab's long guide to running a company with no offices. It is rich in practice on asynchronous communication and documentation, which matters when your colleagues include agents and time zones.
GitLab
GitLab's public guidance on how to give and receive feedback. It explains the Situation-Behavior-Impact way of describing what happened, how to prepare for a hard conversation, why to write feedback down and how habits differ across cultures. Read it with a pen, and ignore the company-specific tools it names.
GitLab
GitLab shows automating the software lifecycle with its agent platform. A practical view of agents across planning, build and review.
GitLab
GitLab's tutorial on building custom AI agents with its Duo Agent Platform. Shows how you can define what an agent does inside your delivery platform.
GitLab
Explains how GitLab tracks alerts and incidents as issues. Check plan availability for each feature.
GitLab
Shows how GitLab runs OpenTofu in pipelines and stores state. Read it to wire plan and apply into merge requests.
GitLab
Shows how to turn labels and milestones into a Kanban-style board in GitLab. Use it to make your work visible in one view.
GitLab
GitLab's reference for issues: what they are, how to create and organise them, and how they link to merge requests. Your day-to-day planning tool on a free account.
GitLab
Explains iterations, GitLab's time-boxed sprint feature. Check the page for plan availability. Read it if you run Scrum in GitLab.
GitLab
Explains how to create and use labels to classify issues. Read it to design a small label set (for example epic, bug, blocked) that agents and people both follow.
GitLab
GitLab's index of step-by-step tutorials on Git, merge requests, issues, CI/CD, security and more. Start here to find a guided lesson on the GitLab feature you need.
GitLab
Shows how to require approvals before a merge. Some approval features need a paid plan, so check what your plan includes.
GitLab
How a pipeline can run for a merge request before anything merges. This is how "proof before merge" works.
GitLab
Explains how to review merge requests with comments, threads and suggestions. A clear review is how you steer agents and humans alike. Read it to review faster and better.
GitLab
GitLab's reference for merge requests, the place where an agent's work is reviewed and merged. Read it so you can review agent output through the same door as any other change.
GitLab
Explains how merge trains test each change against the changes queued ahead of it, so the default branch stays green. Check which plan includes the feature.
GitLab
Explains pipelines that test the merge request combined with the latest target branch. They catch the failures that only appear when two good changes meet, which is common when many agents work in parallel. Read it before you add merge trains.
GitLab
Explains GitLab milestones: dated goals that group issues and merge requests, with progress tracking. Milestones are how you give dates to a plan on the free plan.
GitLab
GitLab's operating principles, including bias for action and low level of shame. They show how a company turns values into daily practice and make good material for your own team's rules.
GitLab
Describes how to secure pipelines: protecting variables, restricting runners and controlling who can trigger what. A pipeline is powerful and so is a target. Read it before you let agents change CI configuration.
GitLab
GitLab's public statement of how its product teams make decisions. Read it as a worked example of principles you can write for your own product.
GitLab
Explains how to stop direct pushes and force pushes to important branches such as your default branch. It is the rule that makes review mandatory.
GitLab
How to limit who can deploy to an environment. Use it to build the production approval step.
GitLab
Explains rules that reject pushes by commit message, file type or author. A guardrail that acts before code even reaches review. Check the page for which plan includes it.
GitLab
Explains rebasing and resolving merge conflicts. Conflicts are normal when several agents touch one repository; this helps you judge a resolution.
GitLab
Explains GitLab's REST API basics. It is how automation, schedules and agents act on a project. Read the introduction to learn what automation can touch.
GitLab
How GitLab can deploy a temporary copy of the product for each merge request so reviewers can click it. Great for design and marketing reviewers.
GitLab
GitLab's roadmap view draws epics and milestones on a timeline. Read it to see the shape of a roadmap view, and check which tier offers it.
GitLab
How to run pipelines automatically on a schedule. Scheduled pipelines power nightly builds and recurring checks such as link audits. Read it when you want a job to run weekly without anyone pushing code.
GitLab
Explains how GitLab detects secrets committed to a repository. Read it to learn what leaks look like and how to respond.
GitLab
Explains GitLab's Service Desk, which turns emails from customers into issues. A git-based request intake.
GitLab
How to sign your commits so that GitLab can show they came from you. Read it when you want proof of who wrote a change.
GitLab
Explains the rules keyword that decides when a job runs, for example only on merge requests or only on a schedule. Rules are how you build gates and scheduled jobs. Read it when a pipeline runs too much or too little.
GitLab
How to add static security scanning to a pipeline with one include line. The basic scanners and downloadable reports are in the free tier. Read it to turn on your source-security gate.
GitLab
GitLab's case study of Thales using DevSecOps. A real example of security built into delivery.
GitLab
GitLab's public handbook of how the company works, written down in the open. It is one of the best real examples of handbook-first, written communication at scale. Browse sections that match your role.
GitLab
Explains estimates and time spent on issues. Useful for forecasting. Use estimates as conversation, not control.
GitLab
The official first-pipeline tutorial from GitLab: write a .gitlab-ci.yml file, run jobs in stages and read the results. Take it so you can read any pipeline an agent proposes and see which checks guard your product.
GitLab
A list of GitLab's own tutorials on planning and tracking work with issues, milestones, labels and boards. Pick the ones that match your plan tier.
GitLab
How to build one shared pipeline file and include it in many projects, pinned to a version. It is the technique behind one pipeline template for every product.
GitLab
Shows how pipelines fetch secrets from external secret managers instead of storing them in GitLab. It teaches the right question to ask: where do the secrets live, and who can read them? Read it before you approve a deployment design.
GitLab
GitLab's guide to Git concepts and tasks. A solid reference to keep open when you need to understand what an agent did with branches and history.
GitLab
GitLab's short explainer of Agile delivery and how it connects planning to shipping. Read it to see the same ideas through the lens of a single source of truth.
GitLab
A plain explainer of continuous integration and continuous delivery. Read it first if the terms are new.
GitLab
A plain explainer of DevSecOps: security built into the delivery pipeline rather than added at the end. Read it for the shared vocabulary.
GitLab Unfiltered
A GitLab walk-through of using issues, labels and boards for project management. It works on the free plan and shows the day-to-day planning view.
GitLab Unfiltered
A GitLab walk-through of issues, epics, milestones and roadmaps. Note that epics and roadmaps need a paid GitLab tier, so on the free plan follow the issues, labels and milestones parts.
Go
The official interactive tour of the Go language, run in the browser. Take it for enough reading ability to follow the code of a PHANTOMS TUI app.
Go
The official first Go tutorial: install Go, write a small program and run it. A good first hour before you review any Go code an agent writes.
Documentation for Google's open-source framework for building and orchestrating agents. It offers another take on multi-agent design, workflows and evaluation. Read the concepts to widen your view beyond a single vendor.
A whitepaper from Google's Kaggle generative AI course explaining what agents are, their parts and how they are used. A calm, structured overview if you want the whole picture before the details.
A workbook chapter on turning an SLO into alerts using burn rates, so people are paged for what matters.
A short guide to a four-step way of structuring a coaching conversation, so that the manager asks questions and the other person chooses the next step. It also gives tips for regular one-to-ones, active listening and specific, timely feedback. Use it when you want a feedback talk to end in a decision the other person owns.
The documentation for Google's Gemini API. It gives you a third vendor's view of the same ideas: prompts, tools and structured output. Skim it to keep your concepts provider-neutral.
A module from Google's ML Crash Course on bias, evaluating fairness and mitigation. Product owners are accountable for who their AI feature works for and who it fails. Read it before you ship anything that affects people.
Google's own account of its long study of what good managers do. It lists ten behaviours, such as coaching, not micromanaging, communicating clearly and making strong decisions, and three manager responsibilities: deliver results, develop people and build community. Use the list as a mirror for your own habits, remembering it describes Google's people and Google's data.
How Gemini models call functions and tools. Reading the same concept from a third vendor confirms the pattern is shared across the industry.
Google's published guides to code review. The reviewer's guide is directly useful for reviewing agent output.
The official help page for Google Scholar. It explains how to search for papers, find the full text through a library link, follow the Cited by link, set email alerts, save articles and export citations. It also states how complete the coverage is. Use it to find a paper that an agent named and check that it exists.
A chapter on how to run on-call rotations so that services stay reliable and people stay well, covering workload balance, safety and operational overload. Read it before you agree an on-call arrangement for your team.
A chapter that explains why perfect reliability is the wrong goal and how error budgets balance speed and safety. It is the base for the service level ideas in this program. Read it slowly; the ideas matter more than the maths.
Describes incident roles, a clear command structure and a live incident document. It supports the idea of a named human commander. Read it before the incident rehearsal.
Explains how to learn from failure without blame and how to make reviews useful. It pairs well with the five-whys method. Read it before you write your first review.
Defines SLIs, SLOs and SLAs and shows how to choose them. It gives the vocabulary for the service level sheet in the capstone. Read the first sections for the definitions.
Google's hub for SRE books and articles. Browse it to find case studies and guides.
Google's coding style guides for many languages. Giving a style guide to an agent is a simple way to make its code consistent.
Free short courses on writing clearly for engineers: short sentences, active voice, good lists. The habits make epics and issues easier to read. Start with the first course.
A multi-course programme from Google on Coursera that covers UX research, personas, journeys, wireframes, prototypes and testing. Coursera sets the price and any financial aid, so check Coursera before you start. Take it if you want a structured, certified route into design after you finish the Dojo exercises.
Google's open repository of examples and guides for the Gemini API. Use it for concrete examples when you evaluate whether to build on Google's models.
A workbook chapter with practical steps and examples for setting SLOs and using error budgets.
Explains how Google crawls, indexes and ranks pages. Useful for understanding why a new site is or is not found.
Teaches how to decide whether a problem suits machine learning and how to state it. Deciding what to build and why is the manager's job, so this is directly on target. Read it before you propose any AI feature.
Google's original checklist of questions asked before a launch: architecture, capacity, failure modes, security, rollout. Copy the shape of it to build your own go/no-go list.
Google's free self-study course on machine learning, with videos, readings and exercises. It explains how models learn from data, which helps you judge what an AI system can and cannot do. Optional but valuable background.
Google's design system documentation. It shows how a design system makes interfaces consistent and accessible. Read the foundations for the principles.
The SRE book chapter on what to monitor, with the four golden signals: latency, traffic, errors and saturation.
Google's published principles for responsible AI. Reading several companies' principles side by side is good practice for writing your own. Note how principles become reviews and policies.
Google's guidebook on designing human-centred AI products, with patterns on user needs, trust, errors and feedback. It covers the product and design decisions around AI that engineers cannot make for you. Read it when you design an AI feature.
Google's guide to prompting Gemini models: clear instructions, examples, context and constraints, and how to iterate. A third vendor view that confirms the habits are shared across models.
A guide of practical rules from engineers who ship ML products. Its advice to start with a simple baseline and to measure before you tune carries over to AI features in general.
Google's basic guide to making a website findable. Required reading before you launch a product website.
Google's re:Work guide to objectives and key results (OKRs): how to write an objective, how to choose measurable key results and how to review them. Use it when you write ORBITAL objectives and indicators, to make sure each objective has numbers that prove it.
The free online edition of Google's book on running reliable systems. You do not read it end to end: pick the chapters on service level objectives, monitoring, incidents and postmortems.
The companion workbook with practical examples of applying SRE ideas. Use it to turn the SRE concepts into practice.
A guide from Google's people-research team on what made some of its teams more effective than others. It names five things that mattered most, among them psychological safety, dependability and clear structure and goals, and it shows the survey questions the team used. Read it before you write expectations for a team, and note that it is research from one company, so treat it as a strong hint, not a law.
Google Cloud
Google Cloud's guide to designing consistent, resource-oriented APIs: naming, standard methods, errors, versioning and more. It is long, so read the introduction and the sections on naming and errors first. Use it to judge whether an API that an agent proposes follows clear conventions.
Google Cloud
Google Cloud's explanation of when and how to write an architecture decision record: when you face a choice with no existing basis, when two or more options exist, and when a solution is not written down anywhere the team can find it. It lists a typical outline (context, requirements, options, decision and reasons). The examples are about cloud infrastructure, but the habit of keeping the record near the code is the same for product decisions.
Google Cloud
Shows how to set a budget and alerts on Google Cloud so a mistake cannot run up a bill unseen. Do this before any hands-on work.
Google Cloud
Descriptions of the capabilities that predict delivery performance, from the DORA research. A menu for improving how a team ships.
Google Cloud
Google Cloud's description of its free trial and always-free usage limits. Read the current terms before you sign up.
Google Cloud
Explains Google Cloud regions and zones and how to choose them. A short, clear page on a concept that all clouds share.
Google Cloud
A short, plain explanation by Google reliability engineers of the difference between a service level indicator, objective and agreement. Read it before you write or negotiate a service level with a customer or a team.
Google Cloud
Google's guidance for designing and operating cloud workloads across pillars like security, reliability, cost and operational excellence.
Google Cloud
Google's learning platform, which includes the former Cloud Skills Boost courses and labs. Some content is free and some needs credits or a subscription, so check the page.
Google Cloud
Explains how Google Cloud's identity and access system decides who can do what on which resource. Read it to learn principals, roles and policies in Google's terms.
Google Cloud
Google's guidance and tutorials for using Terraform on Google Cloud.
Google Cloud
Google Cloud's hub for learning, including Google Cloud Skills Boost. Some labs and courses are free and some need credits or a subscription, so check each item.
Google Cloud
A plain-language explanation of cloud computing, its service models and why organisations use it.
Google Cloud Tech
A short Google Cloud video on Kubernetes nodes and the control plane. Helps you follow an architecture diagram.
Google Cloud Tech
Google Cloud's short explainer of Kubernetes. Gives you the picture in under five minutes.
Google for Developers
A short Google for Developers tutorial on building an AI agent with Gemini 3. See how little code an agent can take.
Google for Developers
A Google for Developers look at Gemini 3. Shows what a third major model family offers developers.
Google for Developers
Google's introduction to the Gemini API and AI Studio. A quick way to see how models are called from products.
Google Research
A research paper from Google that introduces the HEART framework for product metrics: happiness, engagement, adoption, retention and task success. Read the introduction and the description of the framework, and use it as a checklist when you choose KPIs.
GOV.UK
A long public guide, published in February 2025 by the UK Government Digital Service, built around ten principles for using AI. Do not read all of it. Read the principles on knowing what AI cannot do and on keeping meaningful human control, and compare them with your own rules for AI-drafted writing.
GOV.UK
A free UK government toolkit of methods for planning when the future is uncertain, such as horizon scanning and scenario planning. It is written for public servants but the methods apply to any product. Use it to turn your list of possible super novas into scenarios and early-warning signals.
GOV.UK
A public-sector guide to learning about users: why, how often and with whom. It is written in plain language and has practical advice for small teams. Use it to plan how you will gather evidence for personas.
GOV.UK
The UK government's open design system: tested components, patterns and guidance. A real example of a design system that agents can be told to follow.
GOV.UK
The United Kingdom's list of SIC codes, published as a condensed list for describing a company's nature of business to Companies House. Use it to find the UK code for your industry and to compare it with NAICS and ISIC.
GOV.UK
Explains content design: start from what users need, then write the simplest content that meets it. Applies to websites, emails and project notes alike.
GOV.UK Service Manual
Point 4 of the Service Standard: make the common tasks simple. Use it as a test for every screen in your mockups.
GOV.UK Service Manual
Point 7 of the Service Standard: why and how to work in short cycles and learn from users. A short read on the purpose of agile working.
GOV.UK Service Manual
The UK government's guide to agile delivery for public services: teams, phases, user stories and how to work in short cycles. Written in plain English, which also makes it good for learners with English as a second language.
GOV.UK Service Manual
A short, neutral introduction to Scrum, Kanban and other agile methods. Use it to compare methods before choosing a working rhythm.
GOV.UK Service Manual
Practical guidance on finding and recruiting people for research, including who to include. Read it when you book your first five interviews.
GOV.UK Service Manual
Describes the alpha phase, where a team tests ideas with prototypes before committing to build. Read it to see how to test a risky idea cheaply.
GOV.UK Service Manual
Describes the beta phase, where a team builds a real service and improves it with real users. A useful picture of what comes after your first demo.
GOV.UK Service Manual
Describes what a discovery phase is for: understanding users and their needs, the problem and what to do next. A clear, public model of how much discovery is enough.
GOV.UK Service Manual
Describes the live phase, where the service is running and the team keeps improving it. Shows that delivery does not end at launch.
GOV.UK Service Manual
Explains how to learn about users and write user needs. Strong guidance on starting from needs, not from solutions.
GOV.UK Service Manual
Explains why and how teams make prototypes to test ideas before building. Read it before you draw your next-version mockups.
GOV.UK Service Manual
An introduction to why accessibility matters and how to build it into a service from the start. A practical starting point for your website checks.
GOV.UK Service Manual
Advice on choosing a name that describes what the service does in words users would use. A useful counterweight to clever names that nobody can search for.
GOV.UK Service Manual
The UK government's 14-point standard for building good services. Even outside government it is a strong checklist for whole-product thinking: understand users, solve a whole problem, make it simple, make it accessible.
GOV.UK Service Manual
Explains how to run a usability test where a person watches someone use a prototype or service and asks questions. Directly useful for testing your website and mockups.
GOV.UK Service Manual
Guidance on writing the words that appear on screens: buttons, labels, errors and instructions. Read it before you write your website copy or review copy produced by an agent.
Grafana
The documentation of Loki, an open-source log aggregation system. Read its concepts page to see how logs are labelled and queried.
Grafana
Hands-on tutorials for dashboards, logs and metrics with Grafana's open-source tools.
Grants.gov
The U.S. government's guide to how grants work, who can apply and how applications are organised. Read it when a funding source becomes part of your plan. Rules differ by country and funder.
Green Software Foundation
A free course from an industry body about building software that uses less energy and carbon. Use it when your Indicators include an environmental measure, so that you can ask better questions about energy and hosting.
Grow with Google
A video from the Google UX Design Certificate that practises empathy maps, personas, user stories and journey maps, then draws a first wireframe. It joins the Dojo weeks 2 and 5 in one sitting.
Grow with Google
A video from the Google UX Design Certificate course introducing user experience design and what UX designers do. A free taste of the Google programme.
Grow with Google
A video from the Google UX Design Certificate on empathy, with activities to understand potential users. It is a good warm-up for persona work.
GV (YouTube)
A workshop from the venture arm of Google that explains how objectives and key results are set and scored, with examples for young companies. Watch it before you write the Objective and Indicators of an ORBITAL.
Harbor project
The official docs for Harbor, an open source container registry with scanning and signing. Use it to learn what a registry does for a team. Read the overview before the install pages.
Harvard CS50
Harvard's free course for business leaders on how technology works and how to decide about it. Very close to the Dojo's audience.
Harvard CS50
Harvard's free course on AI ideas: search, knowledge, learning and language. A rigorous way to understand how it works.
Harvard CS50
Harvard's free introduction to cybersecurity for a general audience. Excellent security literacy for non-specialists.
Harvard CS50
Harvard's free course on databases and SQL. Data literacy for product decisions.
Harvard CS50
Harvard's free Python course. Python is the usual language of data and agent work.
Harvard CS50
Harvard's free course for people who want to understand technology. A gentle start.
Harvard CS50
Harvard's free web programming course. Learn how a web product fits together.
Harvard CS50
Harvard's introduction to computer science, free online with lectures and problem sets. Take it to understand what is under the surface of every product.
Harvard Kennedy School
An open-access research article from the HKS Misinformation Review journal (CC BY 4.0, published 23 February 2021) about teaching students to check an unfamiliar website by leaving it and reading what other sources say, as professional fact checkers do. It reports that after the course far more students left the site to check. The authors say they do not know if the gain lasts. Read it to see why you check a claim away from the page that makes it.
Harvard Library
A short page from a Harvard Library course guide. It names five checks for a source (currency, relevance, authority, accuracy and purpose) and explains what peer review is. It is public and licensed CC BY 4.0. Read it as a second view next to the Berkeley list, and note where the two agree.
HashiCorp
The Get Started tutorial for Terraform on AWS: install, build, change, destroy and use variables. Do it with a free account and destroy everything at the end.
HashiCorp
Explains modules, the way to package and reuse configuration across environments.
HashiCorp
Explains Terraform state: what it stores, why it must be protected and how remote state and locking work.
HashiCorp
HashiCorp's style guide for Terraform. A useful standard to give agents when asking for infrastructure code.
HashiCorp
The main Terraform documentation. Use it to check what an infrastructure file really does.
HashiCorp
The reference for the plan command that previews changes. It is the heart of the review step in an infrastructure merge request.
HashiCorp
Tutorials for Vault, a secrets manager. Learn why secrets are kept outside code.
HashiCorp
HashiCorp's hands-on tutorials for Terraform, from the first resource to state, modules and workflows. Choose a cloud and follow the Get Started track.
HashiCorp
A short introduction to describing cloud resources as code, planning a change and applying it. It explains the plan step that this program asks you to put in the merge request. Read it first, then try a tutorial.
HashiCorp, an IBM Company
HashiCorp's talk on infrastructure as code for software engineers. Explains the practices around it.
HashiCorp, an IBM Company
A short HashiCorp explainer on infrastructure as code. The case for treating infrastructure like software.
HashiCorp, an IBM Company
HashiCorp's introduction to Terraform. A fast way to see what the tool does.
HashiCorp, an IBM Company
HashiCorp's Terraform basics video. Pair with the introduction to follow a small example.
Helm
Explains charts, releases and values in Helm, the package manager for Kubernetes applications.
Hono
The official steps for running Hono on Bun, including serving a small API. Follow it to see the smallest working version of the PHANTOMS API layer.
Hono
The official Hono documentation: routing, context, middleware and where Hono runs. Start here to read the API code in a PHANTOMS repository.
Hono
A short page from the Hono team on why the framework is small and built on web standards. It helps you see why one API code base can move between runtimes.
Hono
The built-in Hono middleware that adds safe HTTP response headers. Read it to know which protections a one-line change can add.
Hono
How to test Hono routes without starting a server, by calling the app directly. This is the pattern behind the fast API tests in the PHANTOMS starter.
Hono
How Hono checks request data before your code uses it, including with Zod. Use it as the reference for the rule that every API boundary validates input.
Interaction Design Foundation
A definition of personas with the steps to build them and the common mistakes. It gives a second view next to the NN/g article. Read the parts on research first.
Kaggle
A free five-day generative AI course from Google and Kaggle. Covers foundation models, prompting, agents and more. Good structured depth.
Kaggle
Kaggle's free data cleaning course. Teaches the unglamorous work behind data decisions.
Kaggle
Kaggle's free data visualisation course. Charts are how data persuades.
Kaggle
Kaggle's free introduction to AI ethics, covering bias and responsibility. Product owners are accountable for these.
Kaggle
Kaggle's free introduction to machine learning. Builds intuition for what models do.
Kaggle
Kaggle's free SQL course. SQL lets you ask your own questions of data.
Kaggle
Kaggle's free course on explaining model decisions. Explainability is part of trust and verification.
Kaggle
Kaggle's free course on pandas, the standard Python data library. Data-handling literacy.
Kaggle
Kaggle's free short Python course with exercises. Gets you reading Python quickly.
Kubernetes
The conceptual guide to Kubernetes objects and architecture. Read the overview pages to be able to follow an architecture review.
Kubernetes
How to tell Kubernetes when your app is alive and ready for traffic. A bad probe causes outages, so read this carefully.
Kubernetes
Task guides for configuring resources, probes and security contexts. They show the settings that make an app reliable and safe.
Kubernetes
A short tutorial for running a small app on a local Kubernetes cluster. It is hands-on proof of the concepts.
Kubernetes
Explains how outside traffic reaches Services inside a cluster. Read it with a note that newer designs may use the Gateway API, which the Kubernetes docs also cover.
Kubernetes
A famous walk-through of setting up Kubernetes by hand to learn what each part does. Not for everyone; skim it to understand how many pieces a cluster hides.
Kubernetes
How to run a Kubernetes cluster in Docker on your own machine. A safe sandbox for letting an agent practise.
Kubernetes
A cheat sheet of common kubectl commands. Use it to read what an agent did on a cluster.
Kubernetes
An introduction to Kustomize, which customises Kubernetes configuration without templates. Common in GitOps repositories.
Kubernetes
The official interactive tutorial: create a cluster, deploy an app, explore, expose, scale and update it. It is the best first hour with Kubernetes.
Kubernetes
The minikube getting-started guide for a local cluster. An easy sandbox for learning.
Kubernetes
The official explanation of what Kubernetes is and why it exists, with the components of a cluster. Read it to get the vocabulary right.
Kubernetes
The Helm quickstart. Helm packages Kubernetes applications as charts, which agents often generate; this lets you read them.
Kubernetes
Explains CPU and memory requests and limits and what happens when a container exceeds them.
Kubernetes
Explains Kubernetes Secret objects and, importantly, their limits: by default they are only base64 encoded. Read the good practices section.
Kubernetes
A checklist of security basics for clusters and workloads. Use it as a review list, not as a guarantee.
Kubernetes
The documentation site of the Kubernetes CLI special interest group, with guides for kubectl and Kustomize, the tool for customising manifests without templates.
Kubernetes
Step-by-step help for debugging Pods and Services: pending, crashing, and not reachable. You will use it often.
Kubernetes
The official Kubernetes tutorials. Start here to run a sample application and see what a cluster does, so cluster diagrams stop being abstract.
Kubernetes
The official guide to Pods, Deployments, StatefulSets, Jobs and the other workload objects. Read the Deployment pages first.
Kubernetes SIG CLI
The reference for Kustomize, which builds Kubernetes configuration from a base plus overlays for staging and production. Read the overview to understand the base and overlay idea. Look things up as you need them.
Learn Git Branching
An interactive, visual game that teaches branching, merging, rebasing and more by moving commits on a diagram. Do it in your browser after you know the basic commands. It makes rebase finally make sense.
Learn Wardley Mapping
A site that teaches Wardley mapping, a way to draw the parts of a product or service and how mature each part is. It offers a free book, tools and a reference library; other material on the site may be paid, so check each item. Use it as a second way of looking at your industry, next to UBF.
Linux Foundation
Guides from the TODO Group on running open source programs inside organisations. Useful when your company wants to use and contribute to open source well.
Linux Foundation
A free self-paced course on DevOps and SRE ideas such as automation, monitoring and incident response. A strong base for the operations half of product ownership.
Linux Foundation
A free self-paced course from the Linux Foundation that introduces Kubernetes architecture and core objects. A good structured follow-up to the official tutorial. Any certificate is separate and paid.
Linux Foundation
The Linux Foundation's free self-paced introduction to Linux, listed at no cost. Servers, containers and agent sandboxes all run Linux. Take part of it so the command line is not foreign.
Linux Foundation
A free short course on open source licence basics. Licence mistakes become product risks, and generated code makes the question more common. Take it before you release anything open source.
Linux Foundation
SLSA, a framework of levels for supply chain security. A clear ladder you can use to say how trustworthy your build process is.
Linux Foundation
Home of SPDX, the other common SBOM format, which also covers licences. Read it with the CycloneDX page so you can say which format your customer or auditor asks for.
Martin Fowler
A short, clear definition of continuous delivery by a well-known author: keep the software always in a releasable state. It gives you a test for your own pipeline.
Martin Fowler
The classic essay on continuous integration: integrate often, keep the build fast, fix a broken build first. The habits are the point, not the tools.
MDN Web Docs
MDN's CSS layout module. Understand how pages adapt to screens.
MDN Web Docs
MDN's CSS basics module. Understand how brand becomes pixels.
MDN Web Docs
MDN's JavaScript module. Basic literacy for reading page behaviour.
MDN Web Docs
MDN's HTTP documentation. Shows how browsers and servers talk, behind every web product.
MDN Web Docs
MDN's web security documentation. A practical reference on browser security features.
MDN Web Docs
MDN's HTML module. Read it to understand the structure of every web page.
Mend Renovate
The official docs for Renovate, a bot that opens merge requests when dependencies have new versions. Read the introduction and the configuration basics. It supports keeping a patched fork close to upstream.
Microsoft
How to add MCP servers so that agents in VS Code can use extra tools. It shows how tool access is granted and approved in a real product. Useful for thinking about least-privilege access.
Microsoft
Microsoft's documentation for its managed agent service. Reading it shows how a cloud provider packages agents, tools and governance. Read it when your organisation is already on Azure.
Microsoft
A free open-source course of lessons on agent design, tools, planning, multi-agent patterns and trust and safety. Use it as a broad tour of how agent systems are built.
Microsoft
Microsoft's guidance for planning and running AI projects, including responsible AI practices. Read the parts on risk and responsible use before you ship an AI feature.
Microsoft
A Microsoft Learn path with modules on building workflows in GitHub Actions. Good guided practice for the ideas of continuous integration.
Microsoft
The documentation for Microsoft's managed Kubernetes. A managed service shows how clouds take on cluster operations.
Microsoft
The documentation for Azure Monitor. Shows how a cloud provider packages metrics, logs and alerts.
Microsoft
Microsoft's overview of its monitoring service for logs, metrics and alerts on Azure.
Microsoft
Practical advice on prompting and reviewing Copilot output. The same habits apply to any assistant. Read it to calibrate how closely to check what an assistant suggests.
Microsoft
Visual Studio Code's documentation on working with AI agents in the editor. It shows how agent features appear to a developer and what a reviewer sees. Skim it to know what your team's tools can do.
Microsoft
Microsoft's guidance on strategy, planning and governance for adopting cloud. It speaks to business decisions as well as technical ones.
Microsoft
The Visual Studio Code documentation. VS Code is a common place for reviewing diffs; learn to use it.
Microsoft
A free Microsoft Learn path on Bicep, Azure's infrastructure-as-code language. A second language shows what is common to all infrastructure code.
Microsoft
A free Microsoft Learn path on using Terraform with Azure. A good guided hands-on.
Microsoft
A free open-source course of 21 lessons with videos and code on generative AI, prompting, responsible AI and building apps. Pick the lessons that match your gaps.
Microsoft
A free Microsoft Learn path on AI applications and agents on Azure. Good guided practice for understanding cloud AI services. Complete modules at your own pace.
Microsoft
A free Microsoft Learn path on GitHub Copilot basics. A guided way to see what an assistant does and how to review it.
Microsoft
A free Microsoft Learn path on GitHub basics: repositories, issues, pull requests and collaboration. The concepts carry over to GitLab.
Microsoft
The Playwright getting-started guide for automated browser testing, a Microsoft open-source tool. Automated end-to-end tests are one of the best ways to verify agent-built features. Read it so you can ask for and read these tests.
Microsoft
The second AZ-900 path: regions, availability zones, compute, networking, storage and identity on Azure. Useful even if you will use another cloud, because the building blocks are alike.
Microsoft
The first path of Microsoft's Azure Fundamentals (AZ-900) study material. It covers cloud models, shared responsibility and cost basics in a vendor-aware but concept-first way.
Microsoft
A free Microsoft Learn path on security, compliance and identity fundamentals such as zero trust and least privilege. Good security vocabulary for decision makers.
Microsoft
Microsoft's open-source SDK for integrating AI models into applications. Read the overview to understand common building blocks such as plugins and planners.
Microsoft
Explains how backlogs at several levels (epic, feature, story) fit together in Azure Boards. Read it to see a four-level plan modelled in a different tool.
Microsoft
A Microsoft Learn module on planning and tracking work in GitHub Projects. The ideas (issues, boards, views) carry over to GitLab.
Microsoft
Microsoft's open-source framework for building agents and multi-agent workflows. It offers one more provider-neutral view of orchestration concepts. Read it to compare with the OpenAI and Google agent kits.
Microsoft
Microsoft's overview of red teaming AI systems: deliberately attacking them to find weaknesses. It teaches you to ask whether anyone has tried to break your agent before users do.
Microsoft
Describes Microsoft's entry-level AI certification. The study material on Microsoft Learn is free; the proctored exam has a fee that varies by country. Consider it only if a credential helps your career story.
Microsoft
Describes Microsoft's entry cloud certification. The study paths are free; the proctored exam has a fee that varies by country. Consider it if a credential helps your career story.
Microsoft
Microsoft's inclusive design toolkit and principles. Strong for thinking about who a product excludes.
Microsoft
Microsoft's secure development practices. A sound menu of practices to expect in any serious project.
Microsoft
A 12-week, 24-lesson open-source curriculum on artificial intelligence. It gives historical and technical context for the current wave of AI. Dip in where your curiosity leads.
Microsoft
An open-source 10-week data science curriculum. Take the early lessons for data literacy.
Microsoft
An open-source curriculum introducing the Model Context Protocol with real-world examples. Use it for a hands-on view of how agents are connected to tools and data.
Microsoft
A 12-week open-source curriculum on classic machine learning with lessons and quizzes. Take part of it for literacy in how models are trained and tested.
Microsoft
An open-source 12-week web development curriculum. Take parts for literacy in what a website is made of.
Microsoft
Explains MLOps as DevOps ideas applied to machine learning: reproducible training, registered models, automated deployment and monitoring. The examples use Azure, but the ideas are not vendor-specific.
Microsoft
Microsoft's AI Red Team summary of a taxonomy of ways agents fail, security and safety. It gives a vocabulary and checklist for risk reviews. Use it when you assess an agent design.
Microsoft
Microsoft's guide to prompt techniques with examples. It is another vendor's expression of the same ideas, useful to confirm what is general.
Microsoft
Microsoft's published principles and how it puts them into practice. It shows principles turned into governance. Compare it with other vendors when you draft your own AI policy.
Microsoft
The official handbook for TypeScript, widely used in agent-built web projects. Read the first chapters so that you can read type definitions.
Microsoft
Microsoft's introduction to work items, boards, backlogs and sprints in Azure Boards. A useful second view on how another tool models epics, features and stories.
Microsoft
Explains how Azure grants access through roles assigned to people and services at a chosen scope. Use it to see the same ideas as AWS and Google Cloud under Azure's names.
Microsoft
Microsoft Learn's overview of DevOps: people, process and products working together to deliver value continuously. Read it as a second opinion next to the Atlassian page.
Microsoft (GitHub)
Microsoft's public guidelines for designing REST APIs: naming, errors, versioning, long-running operations and more. Use them with the Google guide to judge whether an interface drafted by an agent follows clear conventions.
Microsoft Azure
A short Microsoft Azure explainer of how Kubernetes works. A second angle for the same concepts.
Microsoft Developer
Microsoft Developer full course of the AI Agents for Beginners lessons 1 to 10. A free structured tour of agent concepts such as tools, memory and planning.
Microsoft Developer
Microsoft's full 18-part Generative AI for Beginners video series. A structured, free tour of the main ideas, from prompts to application lifecycle.
Microsoft Learn
Reference architectures and guides for cloud systems. Use it to see how a product is split into parts. Read the application architecture fundamentals.
Microsoft Learn
Describes a global entry point that routes web traffic to backends. It helps you read a map where a front door sits before the services. Skim the overview.
Microsoft Learn
Explains serverless functions that run small pieces of code on demand. It helps you read a repository map that lists function apps. A short overview.
Microsoft Learn
Five pillars for judging a cloud design: reliability, security, cost, operations and performance. It gives a checklist mindset for reviewing a product. Read the overview and one pillar.
Microsoft Learn
Explains a cloud service that connects apps and data with workflows built from steps. It shows how an integration can run without a full application. Read it when you list integrations.
Microsoft Reactor
A Microsoft Reactor session on building, scaling and governing AI agents. Governance is the PDM's job at the top of the agent ladder, so this is directly relevant.
Microsoft Reactor
A Microsoft Reactor session on getting started with AI agents. Gives the Microsoft view of what agents are and how teams build them.
Milvus
Shows how to combine vector search with keyword-style search and merge the results. Read it when plain meaning-based search misses exact names or codes.
Milvus
Explains the index types Milvus offers and the trade-offs between speed, memory and accuracy. It gives you the words to question the cost of a retrieval design.
Milvus
A hands-on quickstart that creates a collection, inserts vectors and runs a similarity search. Do it once to see what 'semantic search' means in practice.
Milvus
The official overview of Milvus, an open-source vector database: what it stores, what searches it supports and where it fits. Read it first, then decide whether your product needs it at all.
MIT Missing Semester
A lecture from MIT's Missing Semester that explains Git from its data model upward. Read it when you want to understand why Git behaves as it does, not just which commands to type.
MIT OpenCourseWare
MIT's free classical AI course. Historical foundations for current AI.
MIT OpenCourseWare
MIT's free course on the design of computer systems: reliability, networking and security. Systems thinking for engineered products.
MIT OpenCourseWare
A graduate seminar from 2005 (course 11.233, Urban Studies and Planning) with a syllabus, readings and assignments. It covers narrowing a research interest, mixing numbers and interviews, and the problems of fieldwork. It is written for doctoral students, so skim it: the syllabus and the questions it asks of research are the useful part for a product manager. Licensed CC BY-NC-SA 4.0.
MIT OpenCourseWare
MIT's free introductory finance course. A 2030 PDM needs finance literacy to talk about budgets, value and risk with executives.
MIT OpenCourseWare
MIT's free course on developing new products and services. Direct material for the product development manager role.
MIT OpenCourseWare
MIT's free algorithms course. Optional deep literacy.
MIT OpenCourseWare
MIT's free course on computational thinking and data science. Builds sound data judgment.
MIT OpenCourseWare
MIT's free introductory programming course. A rigorous start in Python.
MIT OpenCourseWare
A free MIT Sloan course on systems thinking and system-dynamics modelling for strategy, change and policy. It is university level, so take it when you want to understand feedback loops and delays in a product or business. Start with the first sessions and the readings.
MIT OpenCourseWare
Free course material from the MIT Sloan School of Management (taught in autumn 2012) on communicating strategically at work: study your reader, your purpose and your setting before you write. It includes lecture notes and written and presentation assignments. Use it to practise writing and speaking to a specific reader.
MIT OpenCourseWare
MIT's free guides on writing, presenting and communicating technical work. Practical templates for clear communication.
MIT OpenCourseWare
MIT's free intro to deep learning with lectures and labs. A sound technical grounding.
MIT OpenCourseWare
A free MIT Sloan course on finding and measuring a market opportunity, then planning and starting a technology-based enterprise, including a business plan. Use its lecture notes and readings when you write your Objective, Resources and Budget, and when you test whether a market is worth entering.
MIT OpenCourseWare
MIT's free course on optimisation for management decisions. Advanced decision literacy for the numerate.
MIT OpenCourseWare
MIT's free course on the tools programmers use daily: the shell, version control, debugging and more. It builds the literacy to read what an agent did in a terminal.
MITRE
A knowledge base of real-world adversary tactics against AI systems. It is the AI counterpart to the ATT&CK matrix. Browse it to see the range of threats.
Mozilla MDN
MDN's guide to the basics of web accessibility, including semantic HTML and keyboard use. A practical companion to the W3C guidance.
Mozilla MDN
MDN's free, structured path through the basics of building for the web. The reference to open when you want to understand something an agent wrote.
National University Library
A page in the Research Process guide that explains a simple search log: the databases you searched, the search terms, the limits you set and what worked. It links a downloadable log file. Use it as a model for the search record in your evidence log.
NCSC
Guidelines from the UK NCSC and international partners on designing, building, deploying and operating AI systems securely. Written for decision makers as well as engineers. Read it for a high-level security checklist.
Nielsen Norman Group
Describes five methods for ranking work on a roadmap and their trade-offs. Use it to choose a defensible order for your epics.
Nielsen Norman Group
An overview of design thinking: empathise, define, ideate, prototype and test. A short frame for the whole loop from discovery to mockups.
Nielsen Norman Group
Explains the empathy map, a four-quadrant picture of what a user says, thinks, does and feels. A quick tool to organise interview notes before you write a persona.
Nielsen Norman Group
Explains how people scan web pages and why headings, short paragraphs and front-loaded words help. Use it when you structure the pages of your site.
Nielsen Norman Group
Explains field studies: watching people in their real setting to learn how they actually work. Helpful when what people say and what they do may differ.
Nielsen Norman Group
A concise NN/g guide to interviewing users, including how to ask open questions and avoid leading ones. Read it before your first interview.
Nielsen Norman Group
A thorough NN/g guide to journey maps: the parts of one, why they help and how to make one. Read it before you draw your user and customer journeys.
Nielsen Norman Group
Explains when to create a customer journey map and how to base it on real data. It helps you tell the customer path from the user path. Read it before you map the buying side.
Nielsen Norman Group
Separates a journey, which follows a person across all touch points, from a flow, which follows steps inside one product. The difference stops you from mapping only the screens of the app. A short read with clear examples.
Nielsen Norman Group
A side-by-side comparison of empathy maps, journey maps, experience maps and service blueprints. Use it to pick the right map for the question you have. It is a one-page decision aid.
Nielsen Norman Group
NN/g's introduction to personas: what they are, what goes into one and how teams use them. Pay attention to the warning that a persona must come from real research.
Nielsen Norman Group
Explains service blueprints, which extend a journey map with the behind-the-scenes people, systems and processes. This is the tool for seeing the whole product, not only the front stage.
Nielsen Norman Group
Defines usability and its parts: learnability, efficiency, memorability, errors and satisfaction. Use it as the vocabulary for your website tests.
Nielsen Norman Group
An NN/g introduction to what user interviews are good for, their strengths and limits, and how to run them. A good companion to the Dojo interview script.
Nielsen Norman Group
A one-page map of research methods and when each fits across the stages of a project. Use it to choose a method instead of defaulting to a survey.
Nielsen Norman Group
The classic NN/g argument for small, repeated tests instead of one large one. It is the reason the Dojo asks for five interviews and five test sessions.
NIST
NIST's taxonomy of attacks on AI systems such as poisoning, evasion and prompt injection. A reference vocabulary for security reviews. Read the introduction for the categories.
NIST
The U.S. standards body's framework for managing AI risk through four functions: govern, map, measure and manage. It is written for organisations, but its habit of naming risks and owners helps any team.
NIST
NIST's framework for organising cybersecurity work: govern, identify, protect, detect, respond and recover. Useful as a shared language with security teams.
NIST
Suggested actions for each part of the NIST AI Risk Management Framework. Use it to turn the framework into concrete checks for a product.
NIST
The short standard definition of cloud computing: five characteristics, three service models and four deployment models. It gives you vendor-neutral words.
NIST
A core set of secure development practices used by many organisations, written for readers who need a formal reference.
NIST
NIST's definition of zero trust: never trust a request because of where it comes from. The mindset applies directly to giving agents access. Read the overview for the principles.
NNgroup
A short NN/g video on the difference between archetypes and personas. Useful when you have patterns but not yet enough detail to write a full persona.
NNgroup
An NN/g video on five common ways teams get discovery wrong. A good self-check on your own discovery plan.
NNgroup
An NN/g video about working with stakeholders as partners during design projects. Read alongside your stakeholder table.
NNgroup
A short NN/g video on the five components of a journey map and why teams use them. Watch it before drawing your first map.
NNgroup
NNgroup on discovery kick-off workshops. A practical technique for starting discovery with stakeholders.
NNgroup
A five-minute NN/g video on common interview mistakes, including leading questions and not probing enough. Watch it right before your first interview.
NNgroup
NNgroup's short video on heuristic evaluation of user interfaces. A fast overview.
NNgroup
A short NN/g video on how broad or narrow a persona should be. It helps you decide how many personas your product needs and who each one covers.
NNgroup
NNgroup on how to conduct a heuristic evaluation. A practical method for judging an interface quickly.
NNgroup
A short NN/g video on what personas are and how they help a team design with real customers in mind. A quick companion to the written article.
NNgroup
A short NN/g video on keeping personas up to date as you learn more. It supports the Dojo habit of marking each line known or guess and revising it.
NNgroup
An NN/g video on the differences between wireframes and prototypes and which audiences suit each. Watch it before you decide how finished your mockups should be.
NNgroup
NNgroup on synthetic users, AI acting as research participants. Useful to understand the limits of AI in user research.
NNgroup
An NN/g video on the steps of making a journey map, combining storytelling and visualisation. Follow it alongside your own map.
NNgroup
An NN/g video on the difference between a user journey and a user flow and when to use each. It helps you keep the journey about the person, not about screens.
NNgroup
An NN/g video on why and how to prioritise, since a product with everything in it is a worse product. Watch it before you rank your epics.
NNgroup
An NN/g video on using risk statements to structure communication, negotiate with the business and argue for or against activities. A useful tool when you defend your roadmap.
NNgroup
An NN/g video introducing roadmaps as a plan for solving user problems now, next and later. Useful framing for ordering your epics.
NNgroup
An NN/g video on building stakeholder engagement into a team's regular routines. It supports the Dojo practice of regular stakeholder notes.
NNgroup
NNgroup's short video on what personas are and why to care. A fast orientation.
NNgroup
NNgroup on why personas fail. Helps you avoid persona documents nobody uses.
Open Policy Agent
Conftest runs Rego policies against configuration files such as YAML and JSON, and fails when a rule is broken. It is the simplest way to check policy-as-data in a pipeline. The labs use it.
Open Policy Agent
Explains using OPA to approve or reject what gets deployed to a Kubernetes cluster. It is policy enforcement at the last gate before production.
Open Policy Agent
Introduces Rego, the policy language of Open Policy Agent. Even if you never write it, seeing policy expressed as data and rules is a good model for governing systems and agents with code.
Open Policy Agent
How to test policies as code. Governing with policy means testing the policy too. Read it to appreciate that guardrails need their own tests.
Open Policy Agent
Shows how to check configuration and changes against policy inside a CI/CD pipeline. This is a concrete example of policy gates that stop bad changes automatically. Read it when you design gates for agent output.
Open Source Initiative
The list of licences approved as open source by the OSI. Use it to check whether a licence is truly open source or only source-available. Read the page on how the approval process works.
Open Source Security Foundation
A free tool that scores the security habits of open source projects, such as review and dependency updates. Use it as one input when you judge the health of a candidate project. A score is a hint, not a verdict.
OpenAI
A PDF guide on when an agent is the right tool, how to choose models, define tools and instructions, and add guardrails and human oversight. Short enough to read in one sitting.
OpenAI
Documents OpenAI's visual canvas for composing agent workflows. A visual tool like this is how non-engineers can prototype and reason about multi-step agent flows. Read it to see agent logic laid out as a diagram.
OpenAI
Describes two ways to orchestrate agents: let a model decide, or control the flow in code. That choice, flexibility against predictability, is central to governing a fleet. Read it before you pick an orchestration style.
OpenAI
OpenAI's overview of building agents with its platform, covering the main building blocks. Use it to learn the shared vocabulary of agents: instructions, tools, hand-offs and guardrails.
OpenAI
The agents section of the OpenAI Cookbook, gathering worked examples of building agents. Use it to compare how agent patterns look across providers.
OpenAI
OpenAI's Build Hour on the Agents SDK, covering how to build and orchestrate agents. A hands-on view of orchestration, one of the four steps of the agent ladder.
OpenAI
OpenAI's collection of worked examples for building with its models, including agents, evaluations and structured outputs. Browse it to see concrete patterns and to give engineers a shared reference. Search by topic when you need an example of a specific technique.
OpenAI
OpenAI's quickstart for making a first API call. Reading it shows how little code a basic AI feature needs, which helps you question estimates. Use it to see what a minimal integration involves.
OpenAI
The evaluation section of the OpenAI Cookbook, with examples of measuring model and agent quality. Read it to learn what a real evaluation looks like before you ask for one.
OpenAI
OpenAI's guide to measuring how well an agent workflow performs. Pair it with Anthropic's evals article to see two vendors' approaches. Read it before you define pass or fail for an agent.
OpenAI
Explains how a model is given functions it can call to fetch data or take actions. It is the same core idea as tool use in other platforms, shown from OpenAI's side. Read it to understand how agents act on your systems.
OpenAI
OpenAI's session on getting started with Codex. Watching a second tool alongside Claude Code shows what is common to all coding agents.
OpenAI
OpenAI's guide to prompting a model for agentic coding and long-context work, with advice on instructions, tool use and planning. Read it next to Anthropic's guide to see which prompting habits transfer across vendors and which are model-specific.
OpenAI
Explains input and output guardrails that check what goes into and out of an agent. It is a concrete picture of automated gates around an AI worker. Read it to see where policy checks can sit.
OpenAI
Explains handoffs, where one agent passes a task to a more suitable agent. It is a precise description of delegation between agents. Read it when you design who does what in a multi-agent flow.
OpenAI
A short OpenAI introduction to Agent Builder, a visual tool for composing agent workflows. Shows how non-coders may design agent flows.
OpenAI
OpenAI introduces its Agents API. A quick view of the building blocks vendors offer for agents.
OpenAI
OpenAI introduces its Codex app for agentic coding. A short look at how another vendor frames delegating coding work to agents.
OpenAI
How to connect models to remote MCP servers in the OpenAI API. It shows that the same open standard works across vendors. Read it alongside the MCP introduction.
OpenAI
Explains how to check text and images for harmful content before or after a model sees them. It is one simple, concrete guardrail. Read it when you design a feature that shows model output to the public.
OpenAI
OpenAI's learning hub with videos, guides and workshops on using ChatGPT and building with the API. Good for getting comfortable with the basics. Content changes, so pick what fits your level today.
OpenAI
The documentation for OpenAI's open-source Agents SDK in Python: agents, tools, hand-offs, guardrails and tracing. Even if you never write the code, reading the concepts shows you what a multi-agent system is made of.
OpenAI
The TypeScript edition of OpenAI's Agents SDK documentation. It matters if your product team works in a JavaScript stack and wants the same agent building blocks.
OpenAI
OpenAI's open-source coding agent that runs in your terminal. Reading its README and docs shows what another vendor's coding agent offers, which is useful for comparing tools. Try it on a small repository you own.
OpenAI
The open-source repository behind the OpenAI Cookbook, with notebooks and guides for the API. Use the repository when you want to read or reuse the underlying examples.
OpenAI
Explains how repeated prompt content can be reused to reduce cost and latency. It is relevant when you budget agent workloads with long shared instructions.
OpenAI
OpenAI's guide to writing instructions that work: message roles, few-shot examples, giving reference text and testing prompts. A good second opinion next to the Claude guide, because the core habits are the same.
OpenAI
OpenAI's list of safety practices for products built on its models: moderate input and output, keep a human in the loop, test adversarially and limit what users can do. Read it before you put AI in front of customers.
OpenAI
OpenAI's guidance on reducing risk when building agents, including prompt injection and tool approvals. Use it as a checklist of risks to raise in any agent design review.
OpenAI
Shows how to make a model return data that follows a schema. Reliable structure is what allows agents and software to pass work between them safely.
OpenAI
Explains grading the full trace of an agent run, not just its final answer. Judging the path as well as the result is how you catch agents that reach the right answer the wrong way.
OpenAI
Shows how to record every step an agent takes so you can review what happened. Traces are how you audit and debug agent work. Read it to learn what visibility to demand from an agent system.
OpenAI
Explains how to define a test for model output, run it on a set of examples and compare changes. Read it to learn why you measure an AI system instead of trusting a few good-looking answers.
OpenAPI Initiative
The OpenAPI Initiative's beginner guide to describing an API in an OpenAPI document, a standard file that says what an API accepts and returns. Use it to write the contract for an interface in the Assist part of STAR, or to check one that an agent drafted.
OpenClaw
Describes the parts of an OpenClaw deployment and how they connect. Read it to see where the trust boundaries sit.
OpenClaw
The official OpenClaw documentation for its agent gateway, tools and setup. Use it to learn what the runtime can do before you decide whether a product needs it.
OpenClaw
The source repository of OpenClaw with its README, releases and issues. Check the release notes and open issues here before you adopt or upgrade the runtime.
OpenClaw
The official guide to allowing and denying tools per agent. It is the page the PHANTOMS security notes point to, and the basis for a deny-by-default agent policy.
OpenGitOps (CNCF)
States the four GitOps principles: declarative, versioned, pulled automatically and continuously reconciled. A short page that gives the idea in a few lines. Read it first, then the tool docs.
OpenSkills
A free, vendor-neutral primer on ITSM that covers requests, incidents, problems and changes, with slides, a cheatsheet, a practice exercise and a quiz. Start here if the terms are new to you.
OpenSSF
The OpenSSF Best Practices Badge programme, a checklist of practices for open source projects. A concrete list to hold a project to.
OpenSSF
A short checklist for deciding whether an open source package is safe enough to depend on: maintenance, popularity, security signals and licence. Hand it to an agent as the review standard when it proposes a new dependency.
OpenSSF
A free Open Source Security Foundation course on secure software development, from requirements to supply chain. Any certificate or exam is separate.
OpenSSF
The OpenSSF's list of security projects such as Scorecard and Sigstore. Browse to know what supply chain tools exist.
OpenSSF
The page that defines SLSA Build Level 1 to 3 and what each level asks of a build system. Use it as a ladder: pick the level that fits your product today and write the next level into your roadmap.
OpenSSF
A specification of levels of build integrity that describes how to prove an artifact came from the source you think it did.
OpenTelemetry
A short vendor-neutral explanation of observability, logs, metrics and traces from the OpenTelemetry project. Read it first.
OpenTofu
The docs for OpenTofu, the open source fork of Terraform. Use them if you prefer a community-governed licence. Most Terraform ideas carry over.
OWASP
OWASP's work on the security of agentic AI, including threat models and guidance. It gathers current community thinking about agent risks. Read it before you scale a fleet.
OWASP
A practical list of risks in build pipelines (who can change them, how secrets are handled, how runners are isolated) with fixes. Use it as a review list for any pipeline an agent writes.
OWASP
The top ten risks specific to APIs. Most modern products are APIs behind interfaces.
OWASP
A detailed list of security requirements you can test an application against. Use it as a reference when you need a rigorous checklist.
OWASP
A large set of short, practical guides on how to build securely, one topic per sheet. Search it when you build login, input handling, secrets or APIs.
OWASP
A free tool that finds known-vulnerable libraries in your project. Read it to understand what dependency scanning does.
OWASP
Guidance on putting security checks into the pipeline. A checklist for what to automate.
OWASP
A deliberately insecure web shop used for training. It lets you try attacks legally and safely on your own machine and see how the Top 10 risks look in practice.
OWASP
A model for measuring and improving an organisation's software security maturity. A management-level framework.
OWASP
The widely used awareness list of the most critical web application security risks. Read each category once and learn the examples.
OWASP
The best-known list of the most serious web application security risks, with plain descriptions and examples. Use it as a checklist of questions to ask whenever an agent builds a web API or page.
OWASP
OWASP's list of the main security risks of applications built on language models, including prompt injection, leaking sensitive data and excessive agency. Read it before you give any agent access to real systems.
OWASP
A deliberately insecure application that you run yourself to practise finding and fixing vulnerabilities with guided lessons. Run it only on a machine you own, never on a network you share.
OWASP
A compact checklist for securing HTTP APIs: authentication, authorization, input checks, status codes and error handling. Use it as a review list when you judge an API that an agent wrote.
OWASP
Practical rules for storing, handing out and rotating passwords, keys and tokens. Read it before you let an agent touch configuration, CI or deployment.
OWASP
An introduction to threat modeling: thinking through what could go wrong before building. A thinking tool for product people.
OWASP
The OWASP guide to testing web application security. Shows what a security test covers.
OWASP
The getting-started guide for ZAP, a free web security scanner. Try it against your own test site.
OWASP Foundation
A talk by Jim Manico on the OWASP Top Ten Proactive Controls. A clear list of security practices to ask for.
PagerDuty
A public, open-source guide to incident response roles, training and practice, from a company that builds on-call software. You can adapt it to your own team.
PagerDuty
A practical page on what an on-call person is expected to do, with advice on backup schedules, escalation timeouts and handing over to the next person. Good for writing your own on-call expectations.
Paul Graham
An essay arguing that building something people truly want is the core of a good startup. It is a plain argument for user value as the test of a product.
Paul Graham
The full index of Paul Graham's essays on startups, products and thinking. Browse it for models of clear writing and for first-hand startup thinking.
Paul Graham
A long essay on how to find and pursue work you excel at. Useful as a career compass for someone aiming to be among the best at product management.
Paul Graham
Paul Graham's advice on finding ideas by noticing real problems. A product development manager should read it to practise spotting problems worth solving before specifying anything for agents to build.
Paul Graham
A classic essay on why meetings cost makers far more than managers. A 2030 PDM manages both people and agents, so this teaches how to protect focused time and schedule your interruptions deliberately.
Paul Graham
A short essay arguing that writing a thing down shows you how little of it you had really worked out, and that the act of writing changes the idea. Read it before you write your first post: it explains why a point of view is something you find by drafting, not something you already hold.
Paul Graham
A short essay on how the idea at the top of your mind shapes your thinking. It is a useful lens for choosing what a product manager should keep in focus.
Paul Graham
A short essay with one practical trick: write in the words you would use in a spoken conversation with a friend. It helps readers who are tempted to sound formal. If English is not your first language, use it as a test: would you say this sentence aloud?
Paul Graham
A short essay on writing in plain words. Clear writing is the core of briefing agents, so this is directly useful for prompt and spec writing.
PGExercises
A free site of graded SQL questions you answer in the browser, from simple selects to joins and aggregates. Practise reading and writing queries so you can check an agent's SQL.
PostgreSQL Global Development Group
The official chapter on dumping, file-level backup and point-in-time recovery. Read it to learn the questions to ask before a product keeps real customer data.
PostgreSQL Global Development Group
The official guide to primary keys, foreign keys, NOT NULL and CHECK rules. Read it to see how the database itself can refuse bad data, whatever the app code does.
PostgreSQL Global Development Group
The official PostgreSQL tutorial: tables, queries, joins, updates and transactions, with small examples. It is the best first read for anyone who must understand the data an agent creates.
Product School
A Product School webinar on continuous product discovery by a Google senior PM. Real practice in a short session.
Product School
A Product School webinar, Product Discovery 101. A beginner introduction.
Product Talk
Teresa Torres explains the tree that links an outcome to opportunities and solutions. It is a practical way to make discovery visible and to brief agents against a clear outcome.
Product Talk
Product Talk's overview of continuous discovery habits. A solid start for building weekly customer contact into your work.
Prometheus
The official overview of Prometheus, the open-source metrics system, and how it collects and stores time series.
Retraction Watch
A guide to searching the Retraction Watch Database, a large list of retracted papers. It says the database now belongs to Crossref and that its data is openly available. It warns that corrections and expressions of concern are not collected completely. Use it to check that a paper an agent cites has not been withdrawn.
Scrum.org
The official, short definition of Scrum by its creators: the accountabilities, events and artifacts, and the commitments behind them. It is the source other guides interpret, and reading the original once is worth it.
Scrum.org
A Scrum.org session giving an overview of the Scrum framework and how it enables agility. A longer, spoken companion to the Scrum Guide.
SDG Academy
A United Nations-backed library of free online courses and talks on sustainable development. Use it when you want a clear background on a goal before you claim that your product supports it.
SEACOM Global (YouTube)
A talk in which Simon Wardley, who created the method, introduces Wardley maps and why mapping the parts of a business helps you decide. Watch it for a second way to picture an industry, then compare it with a UBF galaxy map.
SeaweedFS
Describes how SeaweedFS speaks the S3 protocol that most tools and libraries already know, and what is supported. Read it to see why an S3-compatible store keeps your code portable.
SeaweedFS
The official SeaweedFS wiki: its parts, how to start a cluster, and its features. Use it to understand what running your own object storage involves.
SeaweedFS
The source repository of SeaweedFS with its releases and licence. Check releases and open issues here before you adopt or upgrade it.
SeaweedFS
The official page on securing SeaweedFS: access control and encrypted connections between its parts. Read it before any customer file goes into the store.
shadcn/ui
The shadcn/ui introduction: accessible, copy-into-your-repo components you own and can change. Read it to see why teams and agents like this approach to a design system.
Sigstore
Explains Sigstore, free tooling to sign and verify software artifacts such as container images.
Silicon Valley Product Group
A long-running collection of short articles on product management by an advisory firm for product teams and leaders. Read them selectively, for example on product discovery and on how empowered teams work. They are opinions from experienced practitioners, so compare them with what you learn from your own customers.
Silicon Valley Product Group
An experienced product coach explains why roadmaps often fail and what a useful one looks like. It gives a view that challenges simple feature lists. Read it critically and compare with this program's outcome-based epics.
Silicon Valley Product Group
A short essay that argues for stating problems to solve rather than lists of features. It supports writing epics as changed situations. A good second opinion after the Atlassian guide.
Simon Brown
A simple way to draw software at four zoom levels: context, containers, components and code. It helps you draw the layers of a product so others can follow. Read the introduction page.
SOPS project
Explains how to encrypt the values in a file so the file can sit safely in git. It helps you understand encrypted secrets next to the rule of never committing plaintext. Read the overview and the quick start.
SPDX
The reference list of short licence identifiers such as MIT and Apache-2.0. These identifiers are what you write in a licence check record. Use it as a lookup, not as reading material.
Stanford
Stanford HAI's annual data-rich report on the state of AI. A 2030 PDM needs a reliable view of where AI capability and adoption really stand.
Stanford
Stanford's course on frontier AI systems. Check the page for the current syllabus and materials.
Stanford
Stanford's machine learning course materials. Deep, technical, and optional for literacy in how models are trained and judged.
Stanford
Stanford d.school's practical guide to the design thinking process and its methods. A hands-on source of discovery and prototyping techniques.
Stanford
The d.school's collection of free design tools and guides. Browse for methods to run workshops and interviews.
Stanford
Stanford's free library of talks by entrepreneurs and leaders. Useful for hearing how experienced founders think and decide.
Stanford
Stanford Online's list of free courses. Browse for courses on AI, business and more.
Stanford
Stanford's course on building language models from scratch. Optional deep literacy on what is inside the models your agents use.
Strategyzer
Strategyzer's library of strategy tools and articles. Browse for canvases and methods for business model design.
Strategyzer
The official one-page canvas for describing how a business creates, delivers and earns value, with a free template download. Use it with UBF: UBF shows the world around your product, and the canvas shows the business inside it.
Strategyzer
Strategyzer's official page for the Value Proposition Canvas, which matches customer jobs, pains and gains to what you offer. A practical tool for persona and discovery work.
SVPG
Marty Cagan's article on why empowered product teams solve problems and feature teams merely build requests. It frames the mindset a PDM needs when agents do the building and humans own the outcomes.
SVPG
Describes teams given problems to solve rather than features to build. The same principle applies to delegating to agents: give outcomes and constraints, then review.
SVPG
SVPG's overview of product discovery: testing value, usability, feasibility and viability before building. A foundation for deciding what is worth giving to agents to build.
Tailwind Labs
The official Tailwind CSS installation guide, the entry point to the styling system used in the PHANTOMS+ web variant. Read it to judge whether a design system fits your product.
TED (YouTube)
A TED talk by the investor John Doerr on setting objectives and measurable key results (OKRs). Watch it before you write the Objective and Indicators of an ORBITAL, and keep its main lesson in mind: a goal needs a number that proves it.
The Donella Meadows Project
A well-known essay by the systems scientist Donella Meadows on where a small change can move a whole system, and where effort is wasted. It is dense but rewarding. Read it when you decide where to put your best effort in a product or an organisation, and then use the plain examples from this lesson to test your own system.
The Linux Foundation
A Linux Foundation talk on open source licence compliance in modern development. Licence risk matters more when code is generated.
The Linux Foundation
A Linux Foundation keynote on moving from open source to agentic systems. A high-level view from the cloud native world.
The Linux Foundation
A Linux Foundation keynote conversation with Linus Torvalds. A rare chance to hear the creator of Linux and Git on how he works.
The Linux Foundation
A Linux Foundation talk on how big the problem of licence compliance is for LLM-generated code. Directly relevant to the governance of agents.
The Pragmatic Engineer
The Pragmatic Engineer with Steve Yegge on vibe coding at Amazon and Google. A candid view of how AI-assisted work is changing teams.
The Pragmatic Engineer
The Pragmatic Engineer with Laura Tacho on measuring the impact of AI on software engineering. Directly relevant to judging whether agents pay off.
The Pragmatic Engineer
The Pragmatic Engineer's interview with Uber's first CTO on scaling. Real stories of growing engineering organisations.
The Pragmatic Engineer
The Pragmatic Engineer with Will Larson on the revised rules of engineering management. A view of how technical management is changing.
Turborepo (Vercel)
The official introduction to Turborepo, which runs the tasks of a multi-package repository in the right order and skips work it has already done. Start here before you read turbo.json.
Twelve-Factor project
Twelve short rules for building apps that are easy to deploy and run, including keeping configuration in the environment and treating backing services as swappable. Use it to judge any starter or agent-built project for operations readiness.
U.S. Census Bureau
The Census Bureau's annual statistics on businesses with paid employees, by industry and place: number of locations, employment and payroll. Use it with your NAICS code to find an honest count of businesses in your market. It covers the United States only; look for your own country's equivalent.
U.S. Census Bureau
The official home of NAICS, the industry codes used by the United States, Canada and Mexico. It has a code search, the code structure and the full definitions with what each code includes and excludes. Use it to define the boundary of your UBF galaxy, and always read the definition before you choose a code.
U.S. Occupational Safety and Health Administration
The older four-digit Standard Industrial Classification, still found in many company records, hosted online by the US safety regulator with a search and a page per code. Use it to look up the SIC code for your industry when a partner, database or old document uses it.
U.S. Small Business Administration
A plain guide to writing a business plan from the U.S. Small Business Administration. Use the structure to check that your product plan covers customers, money and operations. Rules and programmes differ by country.
UC Berkeley Library
A library guide with a quick list of six questions for any source: authority, purpose, publication and format, relevance, date and documentation. It adds tips for researching an author and for testing a website. The six questions are a good base for the source checklist you will keep.
United Nations
The United Nations page for the 17 Sustainable Development Goals, with a page for each goal, its targets and its progress. Use it when you choose indicators for a product, and to see which goal your product might support. Pick the goals you can measure; do not claim more.
United Nations Statistics Division
The United Nations Statistics Division page for ISIC, the International Standard Industrial Classification of All Economic Activities, which many national systems are based on. Use it to find the international code for your industry and to download the structure.
United Nations Statistics Division
The official list of the global indicators used to measure progress on the 17 Sustainable Development Goals, with a code, wording and metadata for each. Use it when you pick an SDG indicator for a product: copy the exact wording and code, and say how you would measure it.
University of Illinois Urbana-Champaign Library
A page from a university library guide on Undergraduate Research Basics. It separates a topic from a research question and shows how to narrow a question that is too broad or widen one that is too narrow. Read it before you write your first research question, then apply the same checks to a product question.
University of Virginia (Coursera)
A Coursera course from the University of Virginia on thinking strategically, analysing the competitive environment and recommending a firm's strategy. Coursera usually lets you view lectures for free in audit mode, while graded work and a certificate need payment; availability can change, so check the enrolment page. Take it to learn the vocabulary your finance and strategy colleagues use.
Vercel
The documentation of the AI SDK, a TypeScript toolkit for calling language models through one interface. It is the library inside the PHANTOMS AI adapter.
Vercel
Explains how Turborepo decides a task can be skipped, and what outputs it saves. It shows where a faster pipeline, and a lower CI bill, come from.
Vercel
The official getting-started path for the Next.js App Router: layouts, pages, linking, data and deployment. Read it to follow the folder structure in apps/web.
Vercel
The guide to building a Next.js app as plain static files, and the list of features that do not work in that mode. It explains a key trade-off in the PHANTOMS starter.
Vercel
The official free Next.js course: build a dashboard app step by step with routing, data and styling. Take it to understand what the web layer of a PHANTOMS product can do.
Vercel
How to reach any model server that speaks the common OpenAI-style protocol, hosted or self-hosted, from the AI SDK. This is the exact route the PHANTOMS adapter uses.
Vercel
Explains how the AI SDK hides differences between model providers behind one interface. Read it to understand how a product can swap models without changing product code.
Vercel
How task dependencies are declared and run, including the build order across packages. Read it to judge whether an agent has wired a new package into the task graph correctly.
W3C
A filterable checklist of the WCAG 2.2 success criteria with techniques for each. Use it to write testable accessibility checks for your site.
W3C
The W3C's plain introduction to what web accessibility is and why it matters, including its benefits for everyone. A good first read.
web.dev
A free course on accessibility: colour contrast, focus, keyboard use, semantics and more. It teaches what to check before you accept a page from an agent.
web.dev
A free course on CSS, from the cascade to layout and colour. Read the first modules to understand the styling choices an agent makes on your behalf.
web.dev
Google's free course on forms. Forms are where users meet your product.
web.dev
A free course from the Chrome team on HTML: structure, semantics, forms and media. It gives you the literacy to judge whether an agent's page markup is sound.
web.dev
Google's free course on images on the web.
web.dev
A free course on web performance: what makes pages slow and how to measure it. Use it to set a speed budget for your site.
web.dev
Google's free privacy course for the web. Privacy is a product obligation.
web.dev
Google's free course on progressive web apps.
web.dev
A free course on making sites that work on small and large screens. Use it to write precise acceptance checks for the phone and desktop views of your site.
web.dev
Explains Google's Web Vitals metrics for loading, interactivity and visual stability. Use them as measurable acceptance criteria for a site.
Wikipedia
An encyclopedia article on mission command, the idea of giving subordinates the intent and the limits and letting them choose the method. It is the human origin of writing outcomes, not instructions, for agents.
Wikipedia
An encyclopedia article on how many people one manager can direct, and the trade-off between wide and tall organisations. It is the plain-language background for span limits in a command chain.
Write the Docs
A guide from a community of documentation writers on how to write software documentation. It covers what to include first, simple principles such as being skimmable and current, and keeping text in plain files next to the code. Use it when your write-up is a demo or a how-it-works page that sits in your repository.
Y Combinator
The Startup School curriculum, listing lectures on ideas, product, growth and fundraising. Use it as a map to pick the lectures that help your product work.
Y Combinator
Eric Migicovsky of Y Combinator on how to talk to users. A second view with real examples.
Y Combinator
Y Combinator on how to get AI startup ideas. Useful to see where partners think AI creates opportunity.
Y Combinator
Y Combinator Startup School on how to get and evaluate startup ideas. A tight framework for judging whether a problem is worth building for.
Y Combinator
Michael Seibel on getting and testing startup ideas. A quick way to learn to validate before building.
Y Combinator
Y Combinator on how to get your first users. Useful for planning launch and early feedback.
Y Combinator
Y Combinator on how to keep your users. Retention is the real test of product value.
Y Combinator
Y Combinator on how to talk to users. Direct, practical interviewing guidance that supports discovery work.
Y Combinator
Michael Seibel on how to plan a minimum viable product. A short, blunt guide to scope.
Y Combinator
A short playbook for starting a company, by Sam Altman. Quick to read and good for the product-market fit mindset.
Y Combinator
A free online course on how to start a startup from the accelerator Y Combinator, with videos and exercises on ideas, customers, building and growth. Use it alongside the DREAM and MVP stages, and as a source of practical founder advice. Treat it as one view, and test its advice on your own customers.
Y Combinator
Y Combinator's library of articles and videos on building startups. A broad, practical collection on product, people and growth.
Y Combinator (YouTube)
A lecture from the 2014 Y Combinator "How to Start a Startup" series on how markets, competition and monopoly shape which companies succeed. It is one opinionated view. Watch it to think about the dominant companies in your galaxy, and then test its claims against the evidence in your own industry.
YouTube: Andrej Karpathy
A one-hour talk that explains what a large language model is, how it is trained and where it fails, with no maths wall. Watch it once to build a correct mental picture before you steer agents.
YouTube: Andrej Karpathy
A longer, more detailed talk on how models like ChatGPT are built, why they hallucinate and how to think about their limits. Watch it after the short intro if you want the full picture.
YouTube: freeCodeCamp.org
A long free video course covering AWS fundamentals for the Cloud Practitioner exam. Watch parts of it to learn the services and words, even if you never sit the exam.
YouTube: freeCodeCamp.org
A video crash course that walks through Git and GitHub from the first commit to pull requests. The ideas are the same on GitLab. Watch it if you learn better by seeing than reading.
YouTube: freeCodeCamp.org
A long free video course that builds AWS infrastructure with Terraform step by step. The tool versions have moved on, so use it for the ideas and check the docs for current syntax.
YouTube: TechWorld with Nana
A long free video course on Docker images, containers and Compose. A good way to learn containers before Kubernetes.
YouTube: TechWorld with Nana
A long free video course explaining Kubernetes concepts and showing them hands-on. Use it if you prefer a presenter to documentation.
Zod
The introduction to Zod, the TypeScript library that describes the shape of data and checks it at runtime. It is used in PHANTOMS for API input, configuration and AI output.
No resource matches those filters. Clear a filter to see more.
