#roadmap
Posts
-
Digging into Gradle's Source 1: How I Read It with AI, and the Map
The first post of a series on reading Gradle's source, starting with diagrams and a 3-minute hands-on run that show what Gradle is, how it works and what it is for. It covers which version is read (master, a 9.10.0 development build), how to get the same commit and build Gradle with Gradle inside Docker, a platform map of the roughly one-million-line codebase, the main road one gradle command travels through the client and the daemon to your task action, and how AI-written notes are re-checked against the source.
-
Digging into Gradle's Source 12: Dependency Resolution — From One implementation Line to Jar Files, and Wrapping Up the Series
What does the single implementation line in build.gradle.kts become in the source? This post follows the DependencyHandler.add() call behind the generated accessor, configurations whose roles are split into declare, resolve and consume, resolution that waits until someone asks for the file list, the loop in which DependencyGraphBuilder grows the graph, the LatestModuleConflictResolver that picks the higher of two versions of the same library and the places where strictly and force change that result, and the two-pass lookup that checks the cache before the repositories, together with --offline and the read-only cache — all checked against the source at a fixed commit and with Docker examples. It then wraps up the 12-part series.
-
Digging into Kafka's Source 1: How I Read It with AI, and the Map
The first post of a series that reads the Kafka source — it starts by showing what Kafka is, how it works and what it is for, with diagrams and a 3-minute hands-on run. It covers which version is read (trunk, 4.5.0-SNAPSHOT) and how it relates to the stable 4.4.0, how to get the same source and build it with Gradle in Docker, the processMessages step that generates code from JSON schemas, a module map of the roughly 720,000-line main codebase, the big road one record travels from send() through the disk and replication to poll(), and how AI-written notes are re-checked against the source.
-
Digging into MariaDB's Source 1: How I Read It with AI, and the Map
The first post of a series on reading the MariaDB server's source, starting with pictures and a 3-minute hands-on run that show what MariaDB is, how it works and what it is for. It covers which version is read (the main branch, 13.2.0 alpha) and how it differs from the LTS releases, how to get the same source including submodules and make a Debug build in Docker (including why the build broke on Windows because of CRLF), a folder map of the 2.59-million-line codebase, the big road one query travels from the connection thread to InnoDB as confirmed with a gdb backtrace, and how AI-written notes are re-checked against the source.
-
Digging into nginx's Source 1: How I Read It with AI, and the Map
The first post of a series on reading nginx's source, starting with pictures and a 3-minute hands-on run that show what nginx is, how it works and what it is for. It then covers which version we read (the 1.31.9 mainline development version) and how it differs from stable 1.30.x, how to get the same source and build it in Docker with auto/configure and make, a folder map of the 260,000-line source, the main path one request takes from accept to sendfile — checked with gdb and strace — and how to read with AI while verifying its notes against the source.
-
Digging into Apache httpd's Source 1: How I Read It with AI, and the Map
The first post of a series on reading the httpd source, starting with pictures and a 3-minute hands-on run that show what Apache httpd is, how it works and what it is for. It covers which version is read (trunk, 2.5.1-dev), how to get the same source and build it in Docker (including the places I actually got stuck), a folder map of the roughly 350,000-line codebase, the big road one request travels, and how AI-written notes are re-checked against the source.
-
Digging into Tomcat's Source 1: How I Read It with AI, and the Map
The first post of a series that reads the Tomcat source — it starts by showing what Tomcat is, how it works and what it is for, with diagrams and a 3-minute hands-on run. It covers which version is read (the main branch, 12.0.0-M1) and how it differs from the stable 11.0.x, which Servlet spec version it implements, how to get the same source and build it with Ant in Docker, a folder map of the roughly 740,000-line codebase, the big road one request travels from the Acceptor to your servlet, and how AI-written notes are re-checked against the source.
-
Digging into Spring's Source 1: How I Read It with AI, and the Map
The first post of the Spring source-reading series, starting with what Spring is, how it works and what it is for — shown first through the smallest possible example, pictures and a three-minute exercise. It then explains how an 840,000-line codebase is split into small units and read with the help of AI, how to get exactly the same source, and the order the reading will follow.