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.Chart the career journey
Developer tools have to help pay the bills. Learn what people want from their careers to increase the impact of your product.
Measure the journey
Good vibes are not enough. You need objective measurement of your impact.A system for answering usage questions will help you sleep better.
Mastery of larger context
It’s not enough to know how to use your tools. Developers need to understand the larger context of where your tools create impact.
Peer learning
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.