How to Read a 190-Post Blog: A Map of Sebastian Raschka's Writing

Sebastian Raschka's blog has about 190 posts over thirteen years. A reading order that moves from method to map to practice to the current frontier.

Some blogs are too big to read. Sebastian Raschka’s blog has about 190 posts across thirteen years, from early notes on PCA and naive Bayes to the 2026 notes on attention variants and reasoning models. You can’t read it front to back, and sorting by date won’t help. The useful question is which order to read it in.

One article to read first

His Recommendations for Getting the Most Out of a Technical Book (November 2025) is short and sets the method. It gives five steps for each chapter:

  1. Read it once, offline, without code, for about twenty minutes. Don’t look anything up. The goal is the big picture.
  2. Read it again and type the code yourself instead of copying it. If your results differ from the book’s, check the repository, then package versions, random seeds and hardware, and ask the author last.
  3. Do the exercises. Try properly before looking at the solutions.
  4. Go back over your highlights and notes, and look up what is still unclear.
  5. Use an idea from the chapter in a small project of your own.

He adds that none of this is fixed. A chapter you already know can be skimmed, and one without code skips the code steps. The method is a starting point, not a rule.

It is the right first read because it tells you how to read the other 189: once for shape, once for detail, then build something.

The blog in eight parts

After that, the blog sorts into eight groups.

1. Building from scratch

Code first, with each mechanism built step by step.

2. Fine-tuning and parameter-efficient methods

3. Post-training and reasoning models

4. How architectures evolved

5. Evaluation, paper lists and trends

6. Learning methods and workflow

7. Engineering practice

8. Early classical machine learning (2013-2022)

PCA, LDA, naive Bayes and the model-evaluation series. Skip them unless you need to fill in traditional ML basics. One exception is Losses Learned: Optimizing Negative Log-Likelihood and Cross-Entropy in PyTorch (2022.4), which bears directly on how loss is computed for LLMs.

Suggested reading order

This is a suggestion, not a template.

Now:

  1. Recommendations for Getting the Most Out of a Technical Book
  2. Developing an LLM: Building, Training, Finetuning, the one-hour talk, as a map of the whole field
  3. Building A GPT-Style LLM Classifier From Scratch
  4. Losses Learned, to firm up the loss calculation

After the from-scratch material:

  1. The LoRA series (Parameter-Efficient Finetuning, LoRA, Finetuning Falcon, DoRA from Scratch), then New LLM Pre-training and Post-training Paradigms
  2. Understanding Reasoning LLMs, then the GRPO article
  3. The Big LLM Architecture Comparison

Long-term reference: the yearly paper lists (2024, 2025 January to June, 2025 July to December, 2026 January to May) and the LLM Architecture Gallery.

That order moves from method to map to practice to the current frontier. It works for any large body of technical writing. Pick the article that teaches you how to read the rest, build a frame, then go deeper in the order your work needs.

This post is licensed under CC BY 4.0 by the author.