karpathy

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.

PierceZ

public class EventLiveData extends LiveData<Object> {

    private final int mSubject;
    private final LifecycleRegistryOwner mLifecycle;

    public EventLiveData(@LiveDataBus.Subject int subject, @NonNull LifecycleRegistryOwner lifecycle) {
        mSubject = subject;
        mLifecycle = lifecycle;
    }

wyon

public class BlockDetect {
  
  // BlockDetectByPrinter
  public static void start() {
        Looper.getMainLooper().setMessageLogging(new Printer() {

            private static final String START = ">>>>> Dispatching";
            private static final String END = "<<<<< Finished";

            @Override

IliaEremin

apply from: 'deps.gradle'

// ...

dependencies {
    compile supportLibs
    compile rxJavaLibs
    compile retrofitLibs
    compile okHttpLibs

0312birdzhang

获取问题跟文章
http://v3.wufazhuce.com:8000/api/reading/index/
然后根据essay跟question id进去到不同的详细
http://v3.wufazhuce.com:8000/api/question/1282
http://v3.wufazhuce.com:8000/api/essay/1339

获取首页
http://v3.wufazhuce.com:8000/api/hp/idlist/0
然后通过http://v3.wufazhuce.com:8000/api/hp/detail/1275 进入

qrtt1

project.afterEvaluate {
    def isAndroidLibraryProject = project.plugins.hasPlugin('com.android.library')
    if(isAndroidLibraryProject) {
        task copyDeps(type:Copy) {
            from configurations.compile {
                include '**/*.jar'
            }
            into "./build/intermediates/bundles/release/libs/"
        }
        bundleRelease.dependsOn copyDeps

ruijun

android {
applicationVariants.all { variant ->
        variant.outputs.each { output ->
            if (variant.getBuildType().isMinifyEnabled()) {
                variant.assemble.doLast{
                        copy {
                            from variant.mappingFile
                            into "${projectDir}/mappings"
                            rename { String fileName ->
                                "mapping-${variant.name}.txt"

gabrielemariotti

Centralize the support libraries dependencies in gradle

Working with multi-modules project, it is very useful to centralize the dependencies, especially the support libraries.

A very good way is to separate gradle build files, defining something like:

root
  --gradleScript
 ----dependencies.gradle

ownwell

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">

<!-- Generated by RHY @will_awoke -->

<module name="Checker">

    <property name="charset" value="UTF-8"/>
    <property name="severity" value="warning"/>

lapastillaroja

import android.content.Context;
import android.content.res.TypedArray;
import android.graphics.Canvas;
import android.graphics.Rect;
import android.graphics.drawable.Drawable;
import android.support.v7.widget.LinearLayoutManager;
import android.support.v7.widget.RecyclerView;
import android.util.AttributeSet;
import android.view.View;