In these times i would argue on probably getting the code reviewed by an ai agent which has been specifically trained on code quality, robustness and company or product specific code practices, that reduces the loan on manual reviewing by a large margin
“Don’t anthropomorphise” is fighting the wrong layer. The entire product design of chat interfaces is built to encourage anthropomorphism because it increases engagement. Expecting users to resist that is like asking people not to click notifications. If this is a real concern, it has to be solved at the product level, not via user discipline.
My initial validator enforced “exactly one root span” per trace. That worked locally, but completely broke when continuing traces from another service via traceparent.
Fixing that required changing the invariant to allow:
One root span (local trace), OR
One span whose parent is external (distributed continuation)
That was the moment I realized how subtle distributed tracing actually is.