Eye of the Storm
Archive
Series

Research, in arcs

AI Basics11 posts
A ground-up introduction to working with AI tools — from prompting fundamentals to integrating AI into your development workflow.
Building in Public2 posts
Behind-the-scenes posts on how this devblog gets built — workflow, tooling, and the decisions behind the decisions.
LLM Driven SDLC1 post
How large language models are reshaping every phase of the software development lifecycle — from requirements and planning through implementation, review, testing, and deployment. A practitioner's view of what actually changes when AI enters the loop.
AI Engineering Research2 posts
Deep-dive research notes on building AI-powered tools — from designing LLM-driven requirements generators to understanding architecture, inference, and production AI systems.
On GitHub

Projects in flight

codagatchiTypeScript
A tamagotchi-style desktop pet built with Tauri — a small always-on-top companion whose stats decay in real time and need tending.
groundworkTypeScript
SDLC discipline plugin for Claude Code — requirements, plans, and structured development workflows.
— Updated as projects evolveAll research & projects
ActivityAbout
GitHubXRSS
© 2026 stormbreaker9000 · charted with care
Archive

// series

AI Basics

A ground-up introduction to working with AI tools — from prompting fundamentals to integrating AI into your development workflow.

in progress
Cover image for AI Basics

The Curriculum

  1. The substratewhat the thing is
    1. ✓What a neural network is, at a conceptual level
    2. ✓What "training" means — pretraining, then post-training
    3. ✓Inference vs. training — why one is cheap-ish and the other costs millions
    4. ✓Why models "hallucinate" and what that word actually means
    5. ✓Knowledge cutoffs
  2. The interfacehow you talk to it
    1. ✓Tokens
    2. ✓Context windows
    3. ✓System vs. user vs. assistant roles (the chat format)
    4. ✓Temperature and sampling
    5. ✓Streaming (why responses appear word-by-word)
    6. ✓Structured output / JSON mode
  3. The representationshow it "thinks"
    1. 12Embeddings and vector space
    2. 13Attention — why context length is hard
    3. 14Why transformers won
  4. Extending the modelgiving it more to work with
    1. 15Prompt engineering as a discipline
    2. 16RAG (retrieval-augmented generation)
    3. 17Fine-tuning vs. prompting vs. RAG — when to use which
    4. 18Tools / function calling
    5. 19MCP and the broader "give models access to stuff" ecosystem
    6. 20Multimodality (vision, audio, etc.)
  5. Building with modelsthe engineering layer
    1. 21Agents — what they actually are vs. the hype
    2. 22Evals — how you know your AI feature works
    3. 23Caching, batching, and cost management
    4. 24Latency and why it matters for UX
    5. 25Determinism, or the lack of it, and how to design around it
    6. 26Guardrails and safety layers
  6. The meta layerthings people ask but rarely get good answers to
    1. 27How to pick a model
    2. 28Open vs. closed models
    3. 29What happens to your data
    4. 30Reasoning models vs. regular models — what "thinking" actually means
    5. 31Why benchmarks are mostly bad
    6. 32The pricing model (input vs. output tokens, cached tokens)
01

What a neural network actually is

A neural network is a function with billions of tunable weights fit from examples by an optimizer — not a brain simulation. A ground-up explainer for software engineers on how they actually work.

May 27
02

What training actually means

Training an LLM isn't one step — it's a pipeline. Pretraining (99% of the compute) gives the model its knowledge; post-training (SFT, RLHF) shapes how it behaves. A ground-up map for engineers.

May 30
03

Inference vs. training

Once training ends, the weights freeze. Inference is the read-path — a forward pass run one token at a time, forever. Autoregressive decoding, prefill vs. decode, the KV cache, and the five ways inference differs from training.

May 30
04

Why models hallucinate

Hallucination isn't a bug grafted onto a truthful system — it's the default behavior of a next-token predictor. The same operation produces every correct answer and every confident fabrication. Why it happens, and why grading rewards it.

May 30
05

Knowledge cutoffs: the model thinks it's still last year

A knowledge cutoff isn't a date on a sticker — it's the trailing edge of a distribution, and the model can't reliably see its own boundary. Why frozen weights make every chat a conversation with an archive, and what actually moves the line.

May 30
06

Tokens, Tokenizers, and How Claude Counts Them

How subword tokenization algorithms work under the hood, why they shape context window economics and model accuracy, and what Claude's proprietary tokenizer changes mean for your API budget.

May 13
07

Context windows: the only door into a frozen model

A frozen model has exactly one write surface — the context window. Why it's bounded, why its usable length is far shorter than the number on the model card, and why deciding what to put in it is the core skill of working with LLMs.

Jun 27
08

Roles are a convention, not an architecture

System, user, and assistant are special tokens in one flat sequence that the model was post-trained to honor — not privileged channels. Why the instruction hierarchy is a learned preference, and why that's exactly why prompt injection works.

Jul 04
09

Temperature and sampling: the dice live outside the model

The model emits a fixed probability distribution; everything that feels random happens in the sampler on top of it. What temperature actually does, how top-k/top-p/min-p differ, and why 'temperature 0' isn't truly deterministic.

Jul 08
10

Streaming: publishing, not generating

Streaming doesn't change how a model generates—only how the server delivers what it was already producing one token at a time. What SSE actually is, why TTFT and ITL are different problems, and the engineering a stream forces on you.

Jul 10
11

Structured output: making a text generator return typed data

Structured output is constrained decoding: before the sampler picks, a schema-compiled state machine masks every token that would break your JSON, making invalid shape mechanically impossible. Three tiers of guarantee, why tool calls are the same machinery, and the quality tradeoff nobody warns you about.

Jul 10