Quick reminder that people are still finding the fediverse, so keep coming back to you contact lists on the various sites you follow them to see their new handles.
Mine is @[email protected]
@eddiejaoude I think we do it pretty well, none of us actually feel like "devrel".
We just... do what needs to be done.
A lot of "DevRel" people get really precious about what devrel is, and lose focus on the fact that the job is relationships inside and outside the org.
@aHev@davidfowl@kellabyte@aspiredotdev You are definitely missing a lot of the project if thats your view.
Logs, traces, events, metrics, profiles, SDKs, global semconv, local semconv, proxies, schemas, validations, protocols.
Naming headers isn't even otel, that's W3C.
@kellabyte@davidfowl@aspiredotdev Thats not an "otel" problem, it's a tracing problem
Otel as a project is way more than tracing. For your specific usecase, I'd advice looking at the events spec, its more aligned to emitting "start/end"
Between logs, events, metrics, traces and profiles, we've got you covered
@Aaronontheweb Qualcomm is my long term bet to be honest, even longer is Qant but thats more like a 5 year thing.
There's a lot riding on the next generation of the halo platforms (beyond gorgon). APU and NPU combinations are the future.
@Aaronontheweb This is the whole ball game right now.
Model choice, context size, quantitative, etc. This is what will make or break a good experience with LLMs and everyone else is trying to one shot everything with Opus 4.6 (or even 4.7).
The concurrency stuff is the hard part imo.
@Aaronontheweb Interesting, although i was more interested in your personal hardware. The prefill and TPS can only really come from behind the openai endpoint as its not exposed to the caller.
Those ones I'd love to see them have gen_ai semconv tracing and metrics.
I shall try it next week.
@Aaronontheweb@AkkaDotNET@htmlcsstoimage@getsdkbin I should show you the new canvas for doing those investigations with visuals and human interaction. Not to say Netclaw can't do a good investigation.
@davidfowl I've been toying with the idea of hooking up wispr flow to Copilot during these meeting with the prompt "any time a feature is discussed, spawn a sub-agent to build it and update the agent as the discussion unfolds, when the work is pushed to a PR, tag everyone in slack".