Discover and read the best of Twitter Threads about #DeveloperRelations
Most recents (2)
Even though I haven't been a big fan of Twitter threads so far, a lot of people I know have made 100-tweet threads for @threadapalooza so I thought I'll give it a try as well. I will start with #APIs and hopefully end up connecting them with the #FutureOfWork. Let's go ...
🧵⬇️
🧵⬇️
First of all, when I talk about #APIs, I mean HTTP-based interfaces connecting apps and backend servers as well as different services with each other. For now, the technical details, such as whether they use REST, GraphQL, gRPC etc., shall not matter. (1/100)
When humans interact with computers they require a user interface (UI), and when machines interact with each other they need application programming interfaces (APIs). At the end of the day, however, these have to be implemented by humans. Good #APIDesign considers both. (2/100)
1/ Next up in #ReflectionThreads : Throwing some light on ‘Developer Relations’ (DevRel) as a function.
I'll summarize some experiences from
- My work at a product MNC
- My research + prep work for product startup/s interviews
Read below 👇🏻
#DeveloperRelations #Thread
I'll summarize some experiences from
- My work at a product MNC
- My research + prep work for product startup/s interviews
Read below 👇🏻
#DeveloperRelations #Thread
2/ DevRel is useful for any company which has a tech product and is looking for increasing their developer base. Needless to say, the framework mentioned below would be applicable (at a high level) for various other (non-tech) products as well.
3/ Why DevRel? 🤔
- Engage with a unique audience : Developers
- Reach devs@scale (1:few:many)
- Help devs make *meaningful* solutions
- Receive critical product feedback
- Engage with a unique audience : Developers
- Reach devs@scale (1:few:many)
- Help devs make *meaningful* solutions
- Receive critical product feedback
