See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
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.
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.
A pattern for building personal knowledge bases using LLMs. Extended with lessons from building agentmemory 20K+ Stars ⭐️, 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.
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.
| blueprint: | |
| name: Appliance Notifications & Actions | |
| description: > | |
| # 📳 Appliance Notifications & Actions | |
| **Version: 4.0** | |
| 🤔 Watts your appliance up to, you're always in the know from start to finish! 🛎️🔌💸 |
Some awesome guy has made a repo for this exact thing https://github.com/LongQT-sea/macos-iso-builder
Flash resulting DMG with Rufus
Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...
// see: https://github.com/chadoe/docker-cleanup-volumes
$ docker volume rm $(docker volume ls -qf dangling=true)
$ docker volume ls -qf dangling=true | xargs -r docker volume rm
| #!/bin/bash | |
| # Author: Shoaloak (Axel Koolhaas) 2024 | |
| # Description: Fix iOS binary entitlements/access for "Operation not permitted" | |
| ENTITLEMENT="com.apple.private.security.container-manager" | |
| binaries=("sh" "bash" "zsh" "dash" # Shell | |
| "ls" "cat" "find" "cp" "mv" # File management | |
| "rm" "mkdir" "rmdir" "touch" | |
| "file" "ln" "du" "scp" | |
| "chmod" "chown" "chgrp" # Permissions |
If you are searching Google for "how to replace an old thermostat with a smart thermostat" or "what do my thermostat wire colors mean," you are not alone. Millions of Americans buy a new Nest, Ecobee, or Honeywell thermostat, unscrew their old wall plate, and immediately freeze when they see a tangled mess of random colored wires.
You might be asking yourself:
Guessing the answers to these questions can permanently fry your new device or blow a fuse on your furnace. But there is a much easier way to do this without hiring an expensive electrician. You can now use thermostatwires.com, an incredibly simple AI tool made specifically for USA homes that lets you identify thermostat wires by picture.
All of these diagrams are dynamically rendered during html display by Github, the images generated from text inside the Github-Flavored Markdown. None are static images. Mermaid support was released for Github on 2022-02-14
Pros & Cons:
Notes:
B-->C[fa:fa-ban forbidden], hyperlink and tooltips) are supported by Github.I've had a hard time bringing bluetooth to work on a Raspberry Pi 5 with Ubuntu 24.04 using Pipewire as audio backend. Maybe you run into the same situation and find this helpful.
With the common tutorials on how to enable a bluetooth speaker connection on Ubuntu, there were the following problems for my combination of Ubuntu 24.04 on a Raspberry Pi 5 and using PipeWire (as of July 2024):
Since Ubuntu 22.10, PipeWire is the default soundserver on Ubuntu, so trying to use Bluetooth with PulseAudio as soundserver would mean to uninstall the recommended default and reconfigure the system.