Jan Killian iki

LLM Wiki v2

A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory, a persistent memory engine for AI coding agents.

This builds on Andrej Karpathy's original LLM Wiki idea file. Everything in the original still applies. This document adds what we learned running the pattern in production: what breaks at scale, what's missing, and what separates a wiki that stays useful from one that rots.

What the original gets right

The core insight is correct: stop re-deriving, start compiling. RAG retrieves and forgets. A wiki accumulates and compounds. The three-layer architecture (raw sources, wiki, schema) works. The operations (ingest, query, lint) cover the basics. If you haven't read the original, start there.

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Kerberos cheatsheet

Bruteforcing

With kerbrute.py:

python kerbrute.py -domain <domain_name> -users <users_file> -passwords <passwords_file> -outputfile <output_file>

With Rubeus version with brute module:

Execution order of Jest/Jasmine test code

While tests run in source order, surrounding code does not which can lead to hard to debug issues.

Compare the test file below with the sample output below that and note the order of the log messages.

Key points

Any code not inside of it, beforeAll, afterAll, beforeEach or afterEach runs immediately on initialisation.
This means code at the end of your file runs before even your before hooks.

Reviewer's checklist - How to boost your code review skills

Purpose of my lightning talk is to present insights I've reached as a reviewer/ reviewee in the last couple of months.

I will answer these questions:

What makes a good code review good?
How to build guidelines? Dos and Don'ts.
How to educate dev/team members about the code review process?

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

	import { auth } from '../../firebase/firebase-admin'
	import { NextApiRequest, NextApiResponse } from 'next'

	type NextContextApiHandler = (req: NextApiRequestWithContext, res: NextApiResponse) => Promise<void>

	export interface Context {
	uid: string
	}

	export interface NextApiRequestWithContext extends NextApiRequest {

	rem Written for buggy audio drivers that need to be restarted
	rem In my case, the Claro 8.18 drivers bug out every once in a while on Windows 10, and need restarting to not sound poppy

	@echo off
	goto check_Permissions

	:check_Permissions
	echo Administrative permissions required to run this script. Checking...

	net session >nul 2>&1

-// ==UserScript==
-// @name        Medium: remove location hash
-// @namespace   http://efcl.info/
-// @description Remove location hash from medium
-// @include     https://medium.com/*#*
-// @version     1
-// @grant       none
-// ==/UserScript==
-function removeLocationHash(){

	; AutoHotkey Media Keys
	^!Space::Send {Media_Play_Pause}
	^!Left::Send {Media_Prev}
	^!Right::Send {Media_Next}
	^!NumpadMult::Send {Volume_Mute}
	^!NumpadAdd::Send {Volume_Up}
	^!NumpadSub::Send {Volume_Down}