About DevTools Connect

DevTools Connect started in Daegu when platform leads kept asking the same uncomfortable question: why do our application analytics for developer tool usage inside engineering platforms look healthy while onboarding still stalls on a forgotten CLI? We formed the practice to answer that question with fieldwork, not another dashboard template.

Mission

Help engineering organizations make tooling and investment decisions from usage evidence that engineers would recognize as fair—interviews, careful telemetry reading, and briefs written for people who own budgets and roadmaps.

Working approach

We treat every engagement as a bounded investigation. Sponsors define the decision. We document access and privacy constraints up front. Findings prefer concrete moments—abandoned templates, plugins disabled after a major IDE upgrade, chatops bots that only one squad trusts—over abstract maturity scores.

Relationships with clients are direct. You speak with the people doing interviews and reading event catalogs, not a rotating account layer. When we are wrong about a hypothesis, we say so in the walkthrough and adjust the brief.

Values

• Prefer evidence engineers can dispute over metrics they cannot interpret.
• Keep recommendations sized to the decision, not to a forever program.
• Respect privacy constraints on developer telemetry as seriously as product analytics.

Contact the practice or review current engagements.