AI for engineering leaders
Engineering strategy, AI-native delivery, team design, evaluation, and governance, in the order I would read them.
Press ⌘K anywhere to open
When I want to learn a topic properly, I put together study material on it with AI tools. These are those notes, mostly on AI and engineering, shared in case they help someone else.
These are personal notes, not Coursera courses, and nobody has reviewed them. For courses taught by universities and companies, go to Coursera.
If you want an order to read in, these group related notes. Progress is saved on this device.
Engineering strategy, AI-native delivery, team design, evaluation, and governance, in the order I would read them.
From agent architecture and tools to evaluation, observability, security, and durable execution.
How models work, how they become assistants, how progress is measured, and how governance is evolving.
44 notes
Part 1 of a five-part series on how LLMs work. The forward pass step by step: attention, the residual stream, and where the parameters live.
Part 2. Scaling laws worked out as unit economics: training compute, memory per parameter, parallelism, and why Chinchilla's headline fit didn't replicate.
Part 3. SFT, RLHF and DPO, with DPO's closed form derived step by step, and what that shortcut costs.
Part 4. Read traces and label the failures before picking a metric, then check an LLM judge like any other classifier before trusting its pass rate.
Part 5. Why decoding is limited by memory bandwidth, why the KV cache caps how many users a server can hold, and what that does to serving costs.
Based on Thariq's July 2026 article on how prompting changes for Claude 5 models, with applied modules on CLAUDE.md, skills and tool design.
Skills, CLAUDE.md, memory, retrieval, MCP and subagents compared as different ways to decide what the model sees, and what each one costs per turn.
How Claude Code's extension model is moving from hooks that vote on an action to mods that wrap it, read from a public issue and published source before release.
A close reading of the email exchange Boris Cherny published about AI-written code in an old codebase, and what each side actually argued.
OpenAI's nine-stage agent pipeline, read as a system for deciding what a person should look at rather than a system for writing code.
Anthropic's playbook for running each stage of software delivery with agents, checked against METR, DORA 2025 and other published evidence.
When Sonnet 5.5 is the cheaper pick and when it isn't, what a task really costs on Opus 5.5, and how effort settings change the bill.
Lessons from the Claude Code team on prompt caching, tool design and skills, with the cache treated as part of the architecture and priced out.
Six harness patterns for agents, quarantining untrusted input, and how to run a measured improvement loop with benchmarks, flags and staged rollout.
Eval design, datasets, LLM-as-judge, offline and online testing, and how to read results without fooling yourself.
The 2026 coding agents side by side (Claude Code, Cursor, Copilot, Kiro, Devin and others), with prompting, day-to-day workflows and team practices.
How the Claude Code team reviews code, read against the product docs: approval by risk tier, AI reviewers, and what to do when review never converges.
The CCA-F exam's five domains, with study notes, practice questions and a study timeline.
Self-correcting loops for coding agents, drawn from Addy Osmani, Boris Cherny, Geoffrey Huntley and Peter Steinberger, with code examples and short animations.
Building a daily agent automation that neither repeats nor drops work: bookmarks, ordering of side effects, credentials and budget caps.
What cloud agent sessions are good for, what parallel runs cost in merges and review time, and which delegated workflows carry the most risk.
Five durable-execution platforms compared for agent workloads from their own docs and pricing, with crash recovery, approval gates and spending caps.
Pixels versus accessibility trees, cost per task, how to read the benchmarks, sandboxes, sign-in, prompt injection, and build versus buy.
A hands-on guide to building agents with the Claude Agent SDK: tool use, multi-turn conversations and orchestration patterns.
The Model Context Protocol and what sits around it: primitives, transports, tool design, building servers, multi-agent orchestration and security.
Traces, spans and metrics for agent systems, and how to debug and tune them in production.
Agent architectures, tools, memory, guardrails, evaluation, cost and observability, with case studies of agents running in production.
Building low-latency voice and text apps with the Realtime API: streaming, WebSockets and function calling.
The lethal trifecta, prompt-injection defences that hold up, least-privilege tools, sandbox egress, agent credentials and kill switches.
Which AI laws bind a US SaaS company with EU users and US enterprise customers as of October 2026: the EU AI Act, the federal preemption fight, Colorado, California and Texas.
Epoch AI's estimate of how fast the cost of AI is falling, next to Anthropic's proposal for measuring progress from inside a lab.
Dario Amodei's September 2026 essay laid out as a chain of claims, then tested against its sources and the main objections.
TypeSafe AI's Jev returns typed answers with probabilities instead of chat. What its calibration does and doesn't guarantee, and the economic bet behind it.
The engineering in Google's paper on putting TPUs in orbit: power, laser links between satellites, and radiation, with measured results kept apart from projections.
The model families as of July 2026: mixture-of-experts, open and closed weights, reasoning, multimodal and small models, and what they cost.
Demis Hassabis's July 2026 call for a self-regulatory body for AI, set against Amodei's and Altman's proposals, with the history behind the debate.
Fifteen people at Anthropic, OpenAI, Google, Cursor and xAI worth following on X, what each one works on and what they've been saying.
Reorganising engineering when agents write most of the code: the unit of work, reviewer capacity, junior roles and ladders, hiring, metrics, and a 90-day plan.
Seven organisations launched forward-deployed engineering teams in 2026. A practitioner's argument that they'll fail the same way, fact-checked claim by claim.
Managing managers, org design, hiring, performance, culture, planning, reorgs, remote teams and developer experience.
Internal developer platforms, CI/CD, Terraform and Kubernetes, OpenTelemetry, SRE practice, feature flags and database migrations.
Distributed systems, sharding, caching, load balancing, queues and the CAP theorem, worked through five classic design problems.
The modern data stack: warehouses, dbt, Airflow, Kafka and Flink, data mesh versus lakehouse, experimentation infrastructure and feature stores.
Workers, KV, R2, D1, Pages, Workers AI and Durable Objects, and why coding agents make Cloudflare a good default for internal tools.
Nothing matches. Try another topic or length.