The Paper Timeline
Every architecture on this site got covered as a standalone topic, organized by category (CNNs here, Transformers there, generative models elsewhere) for learnability. This page reconnects them along the one dimension category-based organization hides: time — what came before what, and what each landmark idea was actually responding to.
The Lineage
Click any paper in the lineage to see exactly what limitation of its predecessor it responded to:
Reading the Lineage as a Chain of Answered Questions
Each link above is a direct response to a specific limitation of what came before it — worth tracing explicitly, since this is what makes the timeline more than a list of names:
- AlexNet → ResNet: AlexNet showed depth helps; going much deeper hit a degradation problem (deeper plain networks got worse, not just harder to optimize) that residual connections directly fixed.
- Seq2Seq → Transformer: Seq2Seq's fixed-size context vector bottlenecked long sequences; attention (first added to Seq2Seq, see Sequence Models — Seq2Seq with Attention) fixed the bottleneck, and the Transformer paper's insight was that attention alone, without the recurrence at all, was sufficient and dramatically more parallelizable.
- Transformer → BERT / GPT: the original Transformer was encoder-decoder, built for translation. BERT kept only the encoder for understanding tasks; GPT kept only the decoder for generation — two different halves of the same architecture, specialized for two different jobs (see Attention & Transformers — The Three Transformer Lineages).
- BERT → ViT: BERT proved bidirectional attention-based pretraining works for text; ViT asked whether the same recipe (attention over a sequence of patches, pretrained at scale) works for images too — it does, given enough data, which is precisely the tradeoff Vision Architectures covers.
- GPT-3 → ChatGPT: GPT-3 showed scale alone produces powerful few-shot capability, but the base model wasn't reliably instructable — SFT and RLHF (see Training Pipeline) were the specific fix for turning a capable-but-uncooperative base model into an assistant that follows instructions and refuses appropriately.
- DDPM → Stable Diffusion: DDPM proved diffusion produces high-quality images but was expensive (many denoising steps, in full pixel space); Latent Diffusion (see Generative Models) moved the same process into a compressed latent space, making it cheap enough for consumer hardware.
- ChatGPT → RAG/Agents: a capable, instructable assistant still had frozen, incomplete knowledge and couldn't take action — RAG (see RAG Engineering) and agentic tool use (see Agent Architectures) are the direct responses to those two specific remaining gaps.
- RLHF → GRPO/reasoning models: RLHF optimizes for human-judged response quality broadly; reasoning-focused RL training (see Training Pipeline — GRPO) narrows the same RL machinery toward specifically rewarding correct multi-step reasoning traces, not just generally-preferred responses.
How to Place a New Paper Into This Lineage
When you encounter a new paper, the fastest way to actually understand its contribution is to ask exactly the "prior work" and "extend" questions from How to Read AI Papers: what specific prior approach is this responding to, and what specific limitation of that approach does it fix? A paper that can't be placed onto a lineage like the one above — connected to a clear "before" and implying a plausible "after" — is either genuinely foundational (rare) or hasn't been understood deeply enough yet.
Research Engineering section complete. Next: Interview Prep — where research literacy becomes a specific, testable skill.