Wolven Tech: Rust consulting. AllSource Prime: durable AI memory → https://xitter.cf/t.co/CfdDxoKhs5 Longhand: AI workflows & training → https://xitter.cf/t.co/Rbml5TOtFF

London, United Kingdom
Joined January 2014
1,000 followers. Thank you. Marking it by opening something up: I am taking on fractional full stack AI developer work through Wolven Tech Ltd. Five spots. One is already taken. How it works below.
7
1
17
630
1/6 Get engineers involved before you standardise how the team uses Claude Code or Codex. Pick a real change. Design the harness and review process with the engineers who will build, review and operate it.
🤖 Made with AI
2
2
70
5/6 Run the actual change through the process. Observe missing context, unclear evidence and work waiting for a decision. Let the engineers revise the workflow from those observations. Judge the result against the shared user outcome.
1
3
Custom telemetry destinations introduce failures the product team cannot control. OpenTelemetry's design guide discusses shared and tenant-specific collectors; its resiliency docs describe finite queues and retries. 1/5
🤖 Made with AI
1
17
Disable a test tenant's destination under representative load. Verify resource bounds, the declared loss policy and healthy-tenant delivery. Persistent queues also depend on storage; they do not guarantee lossless delivery. 4/5
1
3
A buffered log can be written after its request context changes. OBI's trace-log correlation report warns that asynchronous writes under backpressure can miss context or carry stale context. 1/5
🤖 Made with AI
1
1
52
Delay output in a representative service and interleave requests. Compare emitted records with the requests that created them. Inspect after the buffer; a log-creation check can miss the later write context. 4/5
1
4
LightOn's OCR report describes normalising equivalent representations before scoring. Footnote formatting can change an edit-distance penalty while leaving the extracted information intact. 1/5
🤖 Made with AI
1
50
Build paired fixtures: equivalent content expressed differently, plus changes that alter information the application needs. Require the latter to remain distinguishable. Keep the fixtures with each normaliser revision. 4/5
1
7
Before using an OCR score to choose a model, identify the normaliser revision and inspect raw output for an example whose score changed. No independent ranking is established by this review. huggingface.co/blog/lightona… 5/5
15