Over time that one document has become a domain-tuned lens, and each meeting both draws on it and sharpens it, which is why the summaries keep getting tighter and need less of my intervention
FireBeyond on Hacker News
In the thread “Ask HN: What are tools you have made for yourself since the advent of AI?”
Helped: Hand-built context document and error table for reconciliation.
Got in the way: OAuth implementation initially struggled due to broken provider tokens.
… The other half is self-improvement: every clarification I resolve gets written back into the context document: its people directory, terminology glossary, and especially the ASR error table, so a garble I corrected once is corrected automatically from then on. Over time that one document has become a domain-tuned lens, and each meeting both draws on it and sharpens it, which is why the summaries keep getting tighter and need less of my intervention. Beyond that: I use a Netatmo weather station which has a RESTful API (or sends to a cloud server that has one) - I pull that information (which I can see on the web and their apps) into my own VictoriaMetrics / Grafana set up on Kubernetes, via a Go app Claude built. …