> ## Documentation Index
> Fetch the complete documentation index at: https://uploop.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to the Devtools Success Guide

> Success in developer tools doesn't have to be mysterious.

**You deserve better** than the spaghetti-against-the-wall, stickers-and-socks, hand-waving approach to making developers engage with your product.

You deserve a clear and rigorous mission:

**Encouraging developers to learn, love and spread your tool**.

Fifteen years into my career working with makers, builders and developers of all stripes, I know what it takes to actually earn and sustain that love.

As a true believer in open source, **I'd hate the idea that you have to hire me to learn this**. The more we *all* understand these concepts, the more profitable developer tools gets to be.

So presented here is how I slice apart the work of getting people to use developer tools.

It's free.

Pay me if you want to go deeper, but if you learn *just* what's written here, you're going to spend much less time spinning your wheels.

## A candle in the dark

A consistent theme repeats itself as I work with developer tools founders: it's just hard to see the non-code problem space.

**That's how we all got lost in the glue trap of "developer relations."** Don't get me wrong: I really love a lot of folks in that role. I've been them.

But lack of definition wastes time and energy, and your team can't afford it.

So let's light up the territory. This guide can't tell you everything, but it can describe four major domains where having a clear plan and opinion will transform your future.

<CardGroup cols="2">
  <Card title="Chart the career journey" icon="compass" href="journey" cta="Dive in">
    Developer tools have to help pay the bills. Learn what people want from their careers to increase the impact of your product.
  </Card>

  <Card title="Measure the journey" icon="ruler-triangle" href="measurement" cta="Let's start counting">
    Good vibes are not enough. You need objective measurement of your impact.

    A system for answering usage questions will help you sleep better.
  </Card>

  <Card title="Mastery of larger context" icon="head-side-brain" href="context" cta="Support developer mastery">
    It's not enough to know how to use your tools. Developers need to understand the larger context of where your tools create impact.
  </Card>

  <Card title="Peer learning" icon="chart-network" href="peer-learning" cta="Build quality community">
    When we say 'community' what we really want is people who will teach each other the best use of a tool. You can build that on purpose.
  </Card>
</CardGroup>