#local-models

1 post on this topic, newest first. all tags →

A local model is good enough for most of my tooling

I moved commit messages, log triage, PR summaries, test naming and half a dozen other small jobs from a hosted API to an open-weight model on my laptop. Cost had nothing to do with it. For this kind of task a 30B model on a MacBook can't be told apart from the frontier, and I'd rather the data never left the machine.

llmlocal-modelsdeveloper-experience+1 more

May 26, 202610 min12 min

~/tips/today — 2026-10-19

~cat tips/today

Never build an index on a live table without CONCURRENTLY

postgresqlmigrations

A plain CREATE INDEX takes a lock that blocks every write to the table for the whole build. On a big table that means minutes of outage that look like a hung app.

CREATE INDEX CONCURRENTLY orders_customer_idx ON orders (customer_id);

It's slower and can't run inside a transaction, so you'll have to tell your migration tool. If it fails halfway, it leaves an invalid index behind, so check pg_index.indisvalid and drop it before you retry.

↵ open y yesterday l ls /tips

esc close