diegohaz

name	orchestrate-background-sessions
description	Run a multi-step task as a coordinator that starts one background Claude Code session (`claude --bg`) for each unit of work, in place of subagents. Use when the user asks for an orchestrating session, a coordinator, or background sessions/threads for a plan with several steps, issues, or pull requests.

Orchestrate background sessions

You are the coordinator. You do not do the units of work yourself. For each unit, you start one background session, wait for its report, verify its result, integrate it, record it, and start the next unit.

Use a background session in place of a subagent because it has its own context window with its own compaction, its own git worktree, and its own model and effort. It also continues when your context is compacted.

pmanot

macOS SQLite database paths and schemas

Path inventory: 2026-01-21. Table inventories: 2026-06-10. macOS build was not recorded in the original inventory.

~ denotes the user's home directory. Paths and schemas vary by macOS version, account configuration, and library location. Listed columns are schema examples; their presence does not establish populated values or retention periods.

Knowledge

~/Library/Application Support/Knowledge/knowledgeC.db

veekaybee

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Pre-Transformer Models

duongdam

#Simple size about 298Mb. Bun v1.0.21

FROM oven/bun:latest as build-stage

WORKDIR /dist

COPY . .
COPY .env.production .env
COPY package.json package.json
COPY bun.lockb bun.lockb

evadne

How to Sell Elixir AGAIN (2023)

Presented by Evadne Wu at Code BEAM Lite in Stockholm, Sweden on 12 May 2023

Synopsis

We have celebrated 10 years of Elixir and also nearly 25 years of Erlang since the open source release in December 1998.

Most of the libraries that were needed to make the ecosystem viable have been built, talks given, books written, conferences held and training sessions provided. A new generation of companies have been built on top of the Elixir / Erlang ecosystem. In all measures, we have achieved further reach and maturity than 5 years ago.

steveruizok

export class Cache<T extends object, K> {
	items = new WeakMap<T, K>()

	get<P extends T>(item: P, cb: (item: P) => K) {
		if (!this.items.has(item)) {
			this.items.set(item, cb(item))
		}
		return this.items.get(item)!
	}

AlexVipond

Vue code review checklist

Double-check all the Vue best practices that are easiest to forget when you’re focused on design and business logic, but hardest to catch with automated tooling.

The answer to every question should be “yes”, and you should aim to spend 10-15 minutes on the entire list after you’ve already had a chance to read and understand the code.

State management

• Is reactive state created & managed where it's needed, instead of further up the component or composable tree?
• Is prop drilling avoided, within reason?
• Is state derived with computed when possible, instead of synced?

franky47

{
  "explorer.experimental.fileNesting.enabled": true,
  "explorer.experimental.fileNesting.patterns": {
    "*.ts": "$(capture).js, $(capture).d.ts, $(capture).test.ts",
    "*.js": "$(capture).js.map, $(capture).min.js, $(capture).d.ts, $(capture).test.js",
    "*.jsx": "$(capture).js",
    "*.tsx": "$(capture).ts, $(capture).*.ts, $(capture).*.tsx",
    "tsconfig.json": "tsconfig.*.json",
    "docker-compose.yml": "docker-compose.*.yml",
    ".env": ".env.*",

AlexVipond

"Effect" is better than "Handle"

A pattern I see everywhere in web dev: people name their event handlers as handle plus the upper-cased name of the event.

function handleClick (event) {...}

function handleKeydown (event) {...}

function handleFocus (event) {...}

marcingolenia

FROM mcr.microsoft.com/dotnet/sdk:5.0
COPY * ./
CMD ["sh", "-c", "dotnet fsi migrateDatabase.fsx \"${DB_CONNECTION}\""]