😫 If you're feeling discouraged or like you're not making any progress, it might mean you're not scoping your projects correctly.
Whether it's #DevRel, side projects, or learning a new coding skill, knowing how to properly scope a project can feel like a superpower. 🧵
1️⃣ Ask yourself: "What's the smallest deliverable I can make that pushes me further towards my goal or dream?"
This could be a short blog post, a 30 second screencast, a small command line app, or part of a new app feature. It needs to be easy to know if it's finished or not.
2️⃣ Adjust the size of that deliverable according to what you can get done in roughly a few days of work.
This isn't a hard & fast rule, but the goal is to keep it under a week so you can build momentum.
💡 Tip: If you don't know how much work you can accomplish in a few days, block off 90 minutes in your calendar to do some deep focused work in that area. That'll give you a frame of reference for what you can or can't do in a few sessions like that.
3️⃣ As you think about scoping for a few days of work, optimize for quality over quantity.
Factor in time you might need for things like publishing, marketing, deployment, cross-posting, etc.
There's great benefit to thoughtfully running through a whole process.
4️⃣ Make the project 10% more difficult than you're comfortable with.
You want it to push you to learn something new without completely paralyzing you.
5️⃣ As you build more skill and experience, you'll be able to scale the amount you can ship in a few days.
You'll get better at the creative side and you'll also get better at building systems around the steps that are time-consuming in the beginning.
🤔 What about bigger initiatives?
Of course not everything can neatly fit into a few days or a week, but the more you can practice slicing off tiny chunks to work through quickly and measure, the better you can adjust course throughout a big project.
✉️ Developer Microskills Newsletter
If you found this thread helpful, you'll probably like my newsletter. Each week I send out a practical, actionable way to improve as a developer and developer advocate. Sign up here: developermicroskills.com
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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:
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!
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:
1. Get amazing idea 2. Buy sweet new domain 3. Tweet about awesome new project 4. `git init` 5. Um...uh...do some planning? 6. You know what, I'm really busy right now. 8. (Secretly abandons dreams)
Here's a framework to help you finish what you start 🧵
💡 First, sort your ideas:
1. Drop it: Seemed like a good idea at the time, but isn't. 2. Defer it: Maybe a good idea, but no time/resources right now. Archive for now. 3. Do it: Good idea that has the potential for $$/impact/career growth.
Not all ideas need to be executed!
🎯 JPS
Can't decide between equally good ideas? Try the JPS method: Just Pick Something. Also known as "Pin the Tail on the Idea" 🐴.
You'll either:
1. Hate it and move on. 2. Learn from it (whether or not you stick with it). 3. Love it and go deeper.