u/n4r735

Hey folks 👋

I'm building an open-source dev tool that turns telemetry data into knowledge graphs that can be used as context in AI coding agents for debugging purposes or improving performance & costs.

Why? My intuition is three fold:

(1) coding agents are much more useful when they understand how a system actually behaves in production, not just what the repo looks like

(2) using raw telemetry data (for example traces) doesn't really work with coding agents at scale

(3) telemetry context graphs might be even cheaper and more efficient to query compared to using raw telemetry data

Before spending too much time on this & going down the rabbit hole, I'm trying to sanity-check my assumptions and assess if this is actually useful for people building/running AI systems in production. Curious to hear from software engineers that have tried something like this: what worked & what didn't, etc.

Happy to hear thoughts directly in the comments and if anyone's interested in helping out with feedback on the actual tool as I build it, please let me know and I can send more details in private - not my intention to spam anyone.

Appreciate it 🙇

Hey everyone,

I'm conducting a study on the use of AI coding agents and their impact on productivity and well-being for developers. Do you mind helping me with this anonymous survey: https://forms.gle/8QDM46LnVHDweV779. It should take around 1–2 minutes to complete.

Thank you for your time and contribution! 🙏

Salutare tuturor 👋

Lucrez la un studiu despre cum folosesc developerii agenții AI de coding și ce impact au asupra productivității și well-being la muncă. M-ar ajuta mult si-as aprecia dacă ați completa acest survey anonim: https://forms.gle/8QDM46LnVHDweV779. Durează cam 1–2 minute.

Mulțumesc mult pentru ajutor și pentru timpul vostru! 🙏

Hey all,

I’ve been working on a small dev tool and I’m thinking about open-sourcing it and potentially selling it to mid-size/enterprise companies. Before I do the classic “throw spaghetti at the wall” launch, I’d like to sanity-check whether it’s actually useful.

My idea: invite ~10 devs, show them the tool/demo for 30–45 mins, get honest feedback, and pay each person $25 for their time. Curious: would you jump on a 30–45 min dev-tool feedback call for $25?

Also, for anyone who’s done this before: how do you get feedback that’s more useful than “yeah, seems cool”?

Mostly trying to decide whether to polish it, OSS it as-is, or let it die in /side-projects.

Hey all,

I’ve been working on a small dev tool and I’m thinking about open-sourcing it. Before I do the classic “throw spaghetti at the wall” launch, I’d like to sanity-check whether it’s actually useful.

My idea: invite ~10 devs, show them the tool/demo for 30–45 mins, get honest feedback, and pay each person $25 for their time. Curious: would you jump on a 30–45 min dev-tool feedback call for $25?

Also, for anyone who’s done this before: how do you get feedback that’s more useful than “yeah, seems cool”?

Mostly trying to decide whether to polish it, OSS it as-is, or let it die in /side-projects.

Hey all,

I’ve been working on a small dev tool and I’m thinking about open-sourcing it and potentially selling it to mid-size/enterprise companies. Before I do the classic “throw spaghetti at the wall” launch, I’d like to sanity-check whether it’s actually useful.

My idea: invite ~10 devs, show them the tool/demo for 30–45 mins, get honest feedback, and pay each person $25 for their time. Curious: would you jump on a 30–45 min dev-tool feedback call for $25?

Also, for anyone who’s done this before: how do you get feedback that’s more useful than “yeah, seems cool”?

Mostly trying to decide whether to polish it, OSS it as-is, or let it die in /side-projects.