You chose RAG. The real work starts now
RAG or fine-tuning gets answered everywhere. The three questions left after it — the key, the model choice, the budget — get answered nowhere.
Tag
Building applications and tools in Go: concurrency, error handling and the standard library.
There are 21 posts with this tag.
RAG or fine-tuning gets answered everywhere. The three questions left after it — the key, the model choice, the budget — get answered nowhere.
Two phases of the same run measured the same service three times apart. What caught the wrong one was not a better statistic but a second method.
Writing a Go CLI is half the work; versioning it, cross-compiling it and distributing it so others can install it effortlessly is the other half.
Architecture decisions stay true on the wiki and rot in the code. archlint enforces the boundaries in architecture.json on every commit, no model.
In a polyglot repo the rule is the same in every language; one architecture.json now enforces Go, TypeScript and Python boundaries in CI.
I added a deterministic flaky-test filter to CommitBrief: it catches hard-coded sleeps and unseeded randomness at commit time, with no model.