The Three Tees of talks
If you give conference talks as part of your DevRel work, there are many ways to structure them. One of the first ones I remember being taught is what I'll call The Three Tees: Tell 'em what you're going to tell 'em Tell '
If you give conference talks as part of your DevRel work, there are many ways to structure them. One of the first ones I remember being taught is what I'll call The Three Tees: Tell 'em what you're going to tell 'em Tell '
If an open source project is created first and then a community grows around it before a commercial offering is available, I'd call this community-led growth (e.g. Redis, Red Hat). If an open source project is created alongside a commercial product (aka "open source core"
If you're the alpha, you probably have the resources to hire an army of developer advocates to maintain your dominance. If you're the underdog, it's going to be an uphill battle to take over the pack. Instead, you could leave and find a new
If complex concepts are ogres 👹 then Shrek was right, ogres are like onions. They have layers. When teaching a complex concept you can start by introducing the outermost layer of high-level explanation, then peel back a layer to explain the next level of detail, and so on until you'
Sorry but no amount of SEO will polish your content turds.
Developers will be the first to sneer at the exchange-email-for-a-url lead magnet because they will (rightly) point out: you don't need my G-D email to download a file. What might make sense to be gated by email? * email-based courses * open source boilerplates * membership signup * web-based content * platform content