openskills.info
Open Course

LLM Foundations

LLM foundations covers the core concepts behind large language models: transformer architecture, tokenization, pre-training objectives, scaling laws, emergent capabilities, and the practical implications of how these models represent and generate language.

itArtificial intelligence and machine learning

Don't Panic — LLM Foundations

A large language model is a neural network with one relentlessly ordinary job: predict the next token. It reads pieces of text, turns them into numbers, and selects another piece. Repeat that at tremendous scale and it can write code, summarize a report, translate a sentence, or produce JSON. This is not a tiny librarian hiding inside a server. It is a very determined pattern completer with an impressive stationery budget.

The trick is the transformer, the architecture that lets each token pay attention to the other tokens in the input. Older language models moved through text in sequence and lost the plot over distance. A transformer can process the input in parallel, which is why a relationship near the start can still matter near the end. Its learned weights carry patterns from training; the prompt supplies the situation at hand. Confusing those two is how a request for current facts becomes an expensive confidence exercise.

Training also has a small bureaucratic arc. Pretraining makes a base model good at continuing text. Post-training, including supervised fine-tuning and reinforcement learning from human feedback, teaches it to behave more like an assistant. During inference, it generates one token at a time. Temperature changes how broadly it samples from possible next tokens. None of this gives it a secret fact-checker, persistent memory, or hands. It needs supplied context, stored state, or external tools for those jobs.

The surprise is that a large context window is still a budget, not a warehouse. Your instructions, history, added documents, and the reply all occupy it. More material can help, but it can also crowd out the answer you needed. The rest of an application matters for the same reason: system prompts shape behavior, tools provide actions and retrieval, memory preserves state, and guardrails check the result. The model is the engine; the surrounding parts are the brakes, map, and inconveniently necessary seat belts.

Read the Intro for the full architecture and training path. Use the Slides when the token-to-transformer-to-application chain needs a quick visual map. Keep the Cheatsheet nearby for parameters, limits, and the difference between a model generating text and a system doing useful work. Then follow the Reference links to move from the mental model to the documentation and papers that make its details less mysterious.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources