Moving from dev to #DevRel is tough - there's no doubt about it! 😬
Even though it's a very fun job, the day-to-day is totally different than the usual sprints & tickets you're used to.
Here is a thread 🧵 on some strategies I've learned to ease the transition:
Even though it's a very fun job, the day-to-day is totally different than the usual sprints & tickets you're used to.
Here is a thread 🧵 on some strategies I've learned to ease the transition:
1️⃣ Embrace the fact that #DevRel is a new set of skills you can learn.
The big shock moving to dev rel is the dizzying # of required skills: content, marketing, speaking, community-building, & more.
Don't resist it: you're a newbie again & it will take time. That's okay!
The big shock moving to dev rel is the dizzying # of required skills: content, marketing, speaking, community-building, & more.
Don't resist it: you're a newbie again & it will take time. That's okay!
2️⃣ Focus on shipping and improving instead of waiting for perfection.
At any given time, you could be doing a zillion different things. Instead of haphazardly bouncing between projects, try to focus on finishing things, no matter how small. More:
At any given time, you could be doing a zillion different things. Instead of haphazardly bouncing between projects, try to focus on finishing things, no matter how small. More:
https://twitter.com/samjulien/status/1343701442079596544
3️⃣ Don't try to automate too quickly.
The volume and variety of tasks you're doing make it tempting to quickly build a bunch of systems. Resist this urge until you've figured out what needs to be cut vs. automated. Automating the wrong things will cause unexpected bugs. 🐛
The volume and variety of tasks you're doing make it tempting to quickly build a bunch of systems. Resist this urge until you've figured out what needs to be cut vs. automated. Automating the wrong things will cause unexpected bugs. 🐛
4️⃣ Be strategic in your priorities.
Prioritize projects that:
- Others depend on (e.g. internal tools, OSS)
- Involve internal collaboration
- Involve external collaboration (streams, joint blog posts, open source, etc)
- Create opportunities for the community
Prioritize projects that:
- Others depend on (e.g. internal tools, OSS)
- Involve internal collaboration
- Involve external collaboration (streams, joint blog posts, open source, etc)
- Create opportunities for the community
5️⃣ Experiment with time-blocking.
I have 3 types of blocks for working on projects:
- 90 mins: dedicated focus time (creative work)
- 1 hr: maintenance (docs, program maintenance, tasks)
- 30 mins: admin & communications
This may look different for you!
I have 3 types of blocks for working on projects:
- 90 mins: dedicated focus time (creative work)
- 1 hr: maintenance (docs, program maintenance, tasks)
- 30 mins: admin & communications
This may look different for you!
6️⃣ Repurpose content to prefer depth over breadth.
Instead of recreating the same simple demo app over and over again, go deeper. Add features, scale it up, add error handling & tests. As you make it more realistic, you can create content across multiple platforms.
Instead of recreating the same simple demo app over and over again, go deeper. Add features, scale it up, add error handling & tests. As you make it more realistic, you can create content across multiple platforms.
7️⃣ Listen to the community for inspiration.
Stuck on what to make your next talk or video on? If your company has a forum or ticket system, your community is probably telling what they need. Look for trends in questions they're asking & create content to solve their problems.
Stuck on what to make your next talk or video on? If your company has a forum or ticket system, your community is probably telling what they need. Look for trends in questions they're asking & create content to solve their problems.
✉️ Developer Microskills Newsletter
If this thread was helpful, you might like my newsletter. Each week, I send out a practical, actionable way to improve as a dev or dev advocate. Tomorrow is about how to prioritize projects! Sign up at developermicroskills.com
If this thread was helpful, you might like my newsletter. Each week, I send out a practical, actionable way to improve as a dev or dev advocate. Tomorrow is about how to prioritize projects! Sign up at developermicroskills.com
• • •
Missing some Tweet in this thread? You can try to
force a refresh
