Blog

Notes from work in progress: what I was trying to understand, where the code broke, how I tested an answer, and what I changed next.

From question to recorded reasoning
  1. 01
    Frame the questionWrite down what is actually unclear
  2. 02
    Try it in codeLet the implementation reveal the problem
  3. 03
    Test the answerVerify it instead of trusting intuition
  4. 04
    Keep the reasoningRecord why the code changed

Browse by project

Projects with the newest content appear first. Each entry stays with its project, from short notes to longer topics explored in full.

02

In progress

Building a CPU from logic gates in Turing Complete

Three long-term learning goals for Turing Complete's sandbox mode, not a fixed schedule: a 16-bit Hack core, then 32-bit RV32I and Armv6-M cores. Each core has an explicit instruction set architecture (ISA); how to build its circuit is worked out during the design.

  • Turing Complete
  • Hack
  • RV32I
  • Armv6-M
6 entriesView project
01

Planning

Building GPT-2 from scratch

A learning project to implement the path from text tokenization to autoregressive training, while keeping the questions, failed assumptions, and verification evidence visible.

  • Python
  • PyTorch
  • NumPy
  • GPT-2 reference implementation
03

Planning

LLM Applications and Agents

Learning to build applications on large language models, in two topics: the harness, the part outside the model that lets it carry out tasks as an agent, and RAG, which has the model answer from external sources. Notes are filed by topic, and each starts from a concrete question.

  • Python
  • FAISS
  • pgvector
  • MCP
  • LangGraph
  • RAGAS
0 entriesView project