Developers will evaporate throughout the process of interacting with your dev tool. That's natural. But... in real life, there are ways to slow down evaporation: * Use filtered water * Use cold water * Don't heat the pot How would these translate? Are there more ways? I have my own thoughts but curious
Previously I discussed the invisible sub-process of boiling developer water on the pour-over diagram (email titled, "Developer temperature (Pour-over, part 3)"). As I hoped, this brought up more questions that we can explore together. Lovely reader Stephen asked: Can you elaborate on "Evaporated developers"? The phrase is interesting to me.
In the previous pour-over part 3, I pointed out that the heating sub-process represents positioning and messaging. So what does the kettle of developer water represent? Clearly, you cannot just take all the city's tap water to brew your coffee. You're taking a slice of the entire market and bringing
In part 2 of the developer pour-over metaphor, I zoomed in on what kind of developer water is used to make community coffee: distilled or filtered, referring to the "richness" of persona development. But there's another aspect to the type of water... the temperature. I've added an annotation that points
Let me introduce the Developer Pour-Over, a way to think about how the culture and practices of DevRel really enable developer adoption. The marketing funnel sits on top of an upside-down adoption funnel, and the critical chokepoint in the middle is the DX & UX onboarding and DevEd learning. You know,
When you build a structure, you need to spend time on getting the foundation right. I know this first-hand building my office in the backyard. The reason is obvious though: you can't build anything without a foundation. And you can't cut corners. Building a level foundation means everything built on
