惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

H
Help Net Security
腾讯CDC
爱范儿
爱范儿
Google DeepMind News
Google DeepMind News
V
V2EX
Blog — PlanetScale
Blog — PlanetScale
Engineering at Meta
Engineering at Meta
GbyAI
GbyAI
量子位
F
Fortinet All Blogs
G
Google Developers Blog
T
The Blog of Author Tim Ferriss
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Hugging Face - Blog
Hugging Face - Blog
Last Week in AI
Last Week in AI
T
Tailwind CSS Blog
J
Java Code Geeks
S
SegmentFault 最新的问题
D
Docker
博客园 - 司徒正美
The GitHub Blog
The GitHub Blog
Jina AI
Jina AI
M
MIT News - Artificial intelligence
博客园 - 【当耐特】

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I built an x86_64 kernel from scratch, and it made me hat...
Zackery Saye · 2026-05-20 · via DEV Community

Zackery Sayers

Six months ago, I started building TaterTOS64, an x86_64 kernel. As any systems dev knows, once you hit the 10,000-line mark across a mix of C, Assembly, and Linker scripts, your brain starts to leak. I needed a way to document the architectural "why"—how the interrupt vectors hand off to the scheduler, how the paging logic relates to the physical memory map.

Naturally, I tried the modern approach: I fed the code to LLMs.

The Result was a Disaster.
Generic "AI Doc" tools failed me in three specific ways:

  1. The Context Amnesia: They'd understand a single .c file but completely hallucinate the #include chain. They had no idea where the paging.h constants were actually defined in my repo structure.
  2. The Hallucination Loop: They would confidently explain my scheduler's "logical flow" while citing methods that didn't exist, or worse, misinterpreting raw Assembly entry points as high-level C signatures.
  3. The SaaS Tax: I'm building a local kernel. I don't want to pay $20/mo to a cloud service to "rent" access to my own local documentation pipeline.

Building the Solution: TaterBookBuilder
I decided to stop building the kernel for two weeks and build the documentation compiler I actually wanted. I call it TaterBookBuilder.

Instead of a simple "text-to-prompt" wrapper, I built a deterministic analysis engine first.

How it actually works:

  • Physical Inclusion Graphing: Before the LLM ever sees a prompt, the engine walks the repo and maps every #include (C) and %include (Assembly) to its canonical repository node. No more guessing where types come from.
  • AST-Aware Ingestion: Using Roslyn and custom regex parsers, it builds a logical hierarchy of your system. It identifies "Kernel Boundaries" vs "User Space" based on the directory topology and hot-path signals (like syscall entry points).
  • The "Evidence Map" (The Game Changer): I was tired of second-guessing the LLM. I implemented an Evidence Map system. Every claim the book makes is backed by a deterministic ID that points to a specific file and line range in the repo. If the book says "The scheduler uses a Round-Robin approach," there is a footnote pointing exactly to src/kernel/sched.c:L45-L120.

The Philosophy: Local-First and Perpetual
Documentation is a permanent asset. It shouldn't depend on a cloud subscription.

I'm shipping TaterBookBuilder as a 77MB Linux AppImage. It's completely turnkey—I even bundled a static binary of Pandoc inside it so you don't have to install a single dependency.

And for the pricing? I'm using the JetBrains Model. You buy it once, you own that version forever. You get a year of maintenance, and if you don't want to renew, your documentation pipeline keeps working exactly as it did on day one.

Documentation should be as rock-solid and local as the code it describes.

Check out the workbench and download the trial here:
https://taterlabs.shop/taterbook.html

I'd love to hear from other systems devs—how are you handling the "trust gap" with AI-generated architecture maps?

C #Assembly #SystemProgramming #BuildInPublic #LocalFirst #DotNet