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
Coffee is 98% water so it makes sense to think about what kind of water you use to brew your Jet Black Potion of Stamina. So in the developer pour-over, if we zoom in on what type of developer water are we using, what could we say? Talk to a
I mentioned last week that your community can curate your product's GitHub topic. I also made a side comment that you could watch it to spotlight new community projects. However, watching topics is not as easy as it sounds. I'll go over 5 ways you can do it today but
Recently I wrote about the challenge of communication tools like Slack and Discord locking in knowledge within their walls and not making it easy to find previous discussions. This makes learning less accessible and searchable. Despite this drawback, many companies use Slack and Discord as developer communities and support forums.
A community that learns together is constantly generating valuable knowledge but when those conversations are happening in the halls of Slack, nobody else can listen in and benefit – so you end up with repeat questions and support calls. That's one reason why with Excalibur we've stuck with GitHub Discussions and
A public open source product is a window (or VIEW for you SQL nerds) into your internal culture. It's part of your brand. Lurkers and potential contributors will be watching how you work with new first-time contributors and interact with community members. It's important to set the standards and practices
