Getting started with Claude Code: from install to your first request
Install the coding agent that runs in your terminal and hand it your first task.
Implementation guides, design thinking and troubleshooting. Find them by context and code.
Install the coding agent that runs in your terminal and hand it your first task.
Where to put it, how to write it, how long it should be, and what to use when you need to enforce a rule.
Permission modes that set how often it asks, the evaluation order of allow/ask/deny rules, and the wildcard pitfall.
Plan mode, subagents, worktrees and PR creation: a way of working that follows everyday tasks.
Neurons, layers, loss, gradients and backpropagation. Teach a small network XOR and see, briefly, how deep learning learns.
Tokens, probabilities, temperature and the context window. Run a toy model to see how an LLM builds an answer, and why it gets things wrong.
The Transformer is what computes next-token probabilities inside an LLM. See its overall structure, and compute its core, attention, in a small piece of code.
Cloud APIs and open models, size, MoE, thinking, multimodal and roles. A brief map of how to sort the many LLM models and how to pick one.
An experiment making Claude Code actually read a .env with fake keys. CLAUDE.md was obeyed and a Read deny stopped cat, but grep -r and Python slipped past it. Only the sandbox stopped everything.
The same string has a different “length” in each language. I counted 𠮷野家, a flag and a family emoji in four languages, to see why, and how to handle them without breaking anything.
What a local LLM is and how it differs from a cloud API. Estimate memory, understand quantization, run a model with Ollama, and know where it fits.
How to size the memory beyond the weights (the KV cache), split a model across GPUs, handle MoE, serve several users, and choose a serving tool.
Split documents, search for the relevant parts, and hand them to a local LLM to answer. Build a question-answering system for internal documents in dependency-free Python.
Turn document Q&A (RAG) into a production system many people use. Incremental ingestion, permission filtering, better retrieval, evaluation and operations.
Regions and AZs, the main services, a typical web architecture and the shared responsibility model. Plus the safety settings to make first, and the cost pitfalls.
How to choose technology to build and run with a small team, using the setup of a real web app (React Router, Cloudflare Workers, D1, Clerk) as the example.
Even without a GPU in your own PC, Google Colab's free GPU can run an LLM. Two ways to run one (Ollama and Transformers), what you may use it for, what is prohibited, and how to size the memory.
How to recognize burnout, a way to notice early and step back in small ways, and where to turn so you don’t carry it alone.
How to open several branches at once from a single repository, without stashing or cloning.
Full-text and vector search led us to run PostgreSQL on a VM behind a Workers site. A record of connecting it through Hyperdrive, Workers VPC and Tunnel, separating services with roles, and keeping backups and batch jobs on the VM.
After two tables were shown as one through UNION ALL, a product-code search took 4 seconds. Reproduced locally, IN made the planner walk the whole popularity index. A record of reading the estimates to find the cause, and getting back to 0.3 ms with = ANY(ARRAY(...)).
A record of taking a change from database to production deployment with Claude Code. The AI wrote code and checked it locally; a person merged, ran production and entered secrets. What actually went wrong, and why it still did no harm.