๐ TL;DR
When I published the first edition of Dev Opportunity Radar on May 29, 2026, I had no idea what it would grow into. I just wanted to share opportunities and resources I kept discovering so others wouldn't miss them the way I sometimes had.
25 editions later, I've shared 102 opportunities and learning resources, featured 17 Community Finds from 7 contributors, and built a website to make everything easier to discover.
There's also a little announcement I've been saving for this edition. On October 2, 2026, I secured a
.comdomain for Dev Opportunity Radar! Some of you might have noticed the new link appearing in recent editions, but I hadn't formally announced it. I wanted to save that for this milestone because this project means a lot to me, and I felt it deserved a proper home.In this article, I want to look back at how the idea started, the people who helped it grow, what goes on behind the scenes, and a few things I've learned along the way.
I'm also opening this up as an AMA for anyone curious about starting or running a series on DEV. And if you're already running one, I'd love to hear about your experiences and advice too. There's always something new to learn from each other.
A little warning: this one is going to be long ๐ But we're talking about 25 editions here, so please bear with me. As always, the Table of Contents is there, so feel free to jump to whichever section interests you.
Table of Contents
- Why I Wanted to Write This
- Where It All Started
- From My Radar to Our Radar
- What Happens Behind the Scenes
- Giving the Radar a Home: A Little Special Announcement
- A Few Things This Journey Has Taught Me
- Okay, So What's Next? ๐
- Ask Me Anything ๐
- Quick Links
- Let's Stay Connected
Why I Wanted to Write This
25 editions. I actually had to stop and think about that for a moment.
When I started Dev Opportunity Radar, I wasn't thinking about reaching 25 editions. I didn't have a long-term plan for what it would become, and I certainly wasn't thinking about building a website or getting a domain for it. I just had an idea that I wanted to try.
Now, almost 6 months later, here we are.
I thought this milestone would be a good opportunity to look back, share a little about what happens behind the scenes, and talk about the people and moments that have made this series what it is today.
Before getting into the story, here's a little snapshot of where we are.
A Little Snapshot of the Radar
| Milestone | Where we are |
|---|---|
| Editions published | 25 |
| Opportunities and learning resources shared | 102 |
| Community Finds | 17 |
| Community contributors credited | 7 |
| Website launched | July 14, 2026 |
.com domain secured |
October 2, 2026 |
I'm happy to see these numbers, but they don't tell the whole story.
What started as a weekly collection of opportunities has gradually grown into something I hadn't quite imagined at the beginning. There's a community contributing discoveries, a website where readers can explore opportunities, and a lot of little moments along the way that have made me want to keep doing this.
And I still remember what that very first edition looked like.
So, let's go back to the beginning!
Where It All Started
Before Dev Opportunity Radar existed, I'd already experienced what it felt like to discover an opportunity a little too late.
I'd come across fellowships, grants, hackathons, programs, and useful learning resources after applications had closed or submissions had ended. Sometimes the information was out there, but I simply hadn't come across it at the right time.
I started wondering how many other people were missing out for the same reason.
There are so many opportunities out there, but finding them can take quite a bit of time. You might discover one through LinkedIn, another through a Discord server, and something else through a random post. There's no single place where everything worth checking out is collected.
That's where the idea came from.
On May 29, 2026, I published Dev Opportunity Radar #1 as a new weekly series. The plan was simple: every Friday, I'd share opportunities, programs, events, resources, and other interesting things I came across.
But there was one part of the 1st edition that mattered just as much to me as the opportunities themselves.
I wrote:
The goal isn't for this to become my radar. The goal is for it to become our radar.
I wanted readers to be able to share things they'd discovered too. I knew I wouldn't find everything, and I didn't want the series to become a one-way loop where I published something every week and everyone else simply read it.
That's why I included a Community Finds section right from the first edition. It wasn't something I added later to increase engagement, get more views, or fill space. I wanted readers to have a place to share their discoveries, receive credit when their finds were featured, and help others discover things they might otherwise miss.
I even left that section empty in Edition #1. I didn't know whether anyone would contribute, but I wanted to make room for it from the start.
At the time, I had no idea when the first submission would arrive. Looking back, that little decision became one of my favorite parts of the entire journey.
From My Radar to Our Radar
That original idea started taking shape sooner than I expected. It began with a little encouragement, followed by the first Community Finds, and eventually grew into many different ways people became part of the series.
It Started With a Little Encouragement
When I published the first edition on May 29, I shared it in DEV's Weekly Wins thread.
I'd only started writing regularly about a month earlier, so I was still getting comfortable with publishing articles. I wasn't sure how people would respond to a weekly series like this.
But the response was encouraging. People stopped by, shared their thoughts, followed along, and told me why they thought collecting opportunities in one place could be useful. That gave me a reason to keep going and helped the series reach people I might not have reached otherwise.
And then, after the first couple of editions, something I'd hoped for when starting the series actually happened. Someone sent in a Community Find!
Community Finds: From the First Submission to Where We Are Today
After Edition #2, Julien Avezou was the first person to send in a Community Find for Dev Opportunity Radar. I featured it in Edition #3.
I remember being so happy when that first submission came in. I'd talked about wanting this to become our radar, and now someone had actually taken the time to contribute something to it!
Francis and Phinn also shared Community Finds in Edition #3, so we had 3 contributors right at the beginning. It was lovely to see that little empty section from Edition #1 finally come to life.
And over the editions, more people joined in. So far, we've had 17 Community Finds from 7 contributors:
- Julien Avezou (@javz)
- Francis (@francistrdev)
- Phinn Markson (@marsonp)
- La Shara Cordero (@earlgreyhot1701d)
- Konark Sharma (@konark_13)
- Dhruv Jani (@dj29)
- Boon (@hboon)
To all 7 of you, thank you so much!
One of my favorite things about Community Finds is that I get to discover things through you as well. Some submissions have introduced me to opportunities I probably wouldn't have found on my own.
And I really appreciate the thought behind every submission. You're going about your day, come across something interesting, and remember to send it my way because you think it might be useful to someone following the Radar. I don't take that for granted.
I'd love to see more people take part in this. If you come across a hackathon, fellowship, event, developer community, or learning resource that you think other readers might find useful, please send it my way! You don't need to be a regular contributor, and it doesn't have to be something extraordinary. If you think it's worth sharing, I'd be happy to take a look.
I also want to mention that I review every submission before featuring it, and sometimes there are reasons I can't include a particular find. It could have restrictive eligibility, be limited to a specific location, or simply not be the right fit for the Radar.
If I've ever been unable to feature something you've sent, I'm sorry, and thank you for understanding. I know you've taken the time to find it and share it with me. I don't want you to feel that effort goes unnoticed just because it didn't make it into an edition.
So please don't hesitate to share something just because you're unsure whether it'll be featured. I'd still love to hear about it. And who knows, it might be something I hadn't discovered yet!
Reader Updates: What Happened After You Found Something?
There's one more thing I love hearing about: what happens after someone discovers something through the Radar.
Did you apply for an opportunity you found in an edition? Join a community? Attend an event? Or use a resource that turned out to be helpful? I'd love to hear about it!
I introduced Reader Updates in Edition #5 because I didn't want the story to end once someone found something interesting. I wanted to know what happened next, too.
And we've already had a few updates! Daniel Nwaneri (@dannwaneri) shared that he applied for the FR8 Residency after finding it in Edition #2. Anh (@anhmtk) also shared how OpenAI Build Week, featured in Edition #7, inspired Anh to submit a project.
A big thank you to Daniel and Anh for sharing these updates and giving me permission to feature them! It means a lot to me. When I spend time putting these editions together, I sometimes wonder whether the opportunities and resources are reaching people and making a difference. Hearing from someone who actually took a step because they found something through the Radar gives me a little glimpse of that impact. And that's really encouraging.
So, if you've ever taken a next step because you discovered something through the Radar, feel free to share it in the comments. I'd love to hear about it, and with your permission, feature your update in a future edition!
The Many Ways You've Supported the Radar
Community Finds were one way readers became part of the series. There were also people who helped it grow in ways I hadn't expected.
After Edition #2, Francis invited me to publish Dev Opportunity Radar with The DEVengers. From Edition #3 onward, the editions have been published both on my profile and through The DEVengers.
I'm still the one doing the research, reviewing submissions, selecting opportunities, and putting each edition together. But having another place to publish the series has helped it reach readers who might not have come across it otherwise. Thank you, Francis, for the invitation and for making room for the Radar there!
Daniel Balcarek(@gramli) and Francis have been giving Gems to my editions ever since the feature came out. I've noticed it, and I just wanted to say thank you both for the support. It means a lot ๐
I also wanted to give a little shoutout to some familiar faces I've noticed regularly reacting to the editions: Web Developer Hyper, Lingfeng, Omar, Shubhra, Klaudia, Divya, csm, Nyaomaru, Fenix, Vinicius, Fayaz, Nnamdi, Hanzla, BuildBaseKit, Scarab Systems and Nicholas Thank you for being here and following along ๐
And of course, I don't want to make this only about the people I've mentioned by name. There are so many others who have been part of this journey in different ways. Those who leave reactions, share comments, offer feedback, suggest improvements, share the editions with others, or simply stop by to read every week.
Even if you've never commented or reacted to an edition, I want you to know that I'm grateful you're here too. I know not everyone expresses their support in the same way, and that's perfectly okay.
So, a big thank you to everyone who has been reading, supporting, sharing, and being part of Dev Opportunity Radar in your own way. Whether you've been here since Edition #1 or just came across the series recently, I'm really happy you're here ๐
I may be the one putting everything together every Friday, but the people who have contributed, encouraged me, shared their thoughts, or quietly followed along have made this experience much more meaningful than I expected when I started.
What Happens Behind the Scenes
Okay, we've talked about how Dev Opportunity Radar started, how the community became part of it, and everything that's happened over these 25 editions. Quite a bit of serious talking, hasn't it?
Now, let's get into the actual research and putting together each edition. I have a feeling this might be the slightly boring part for some of you, so let me try to make it a little more fun to read!
And just so you know, writing funny things doesn't come naturally to me. I'm trying here, so please appreciate the effort ๐
Finding Opportunities (There's No Magic Website!)
Let's start with the obvious question: where do I actually find all these opportunities?
Well, unfortunately, there's no single magical website where all the good opportunities are listed in one place. Wouldn't that make life so much easier?
I look through company pages on LinkedIn, hackathon platforms, X, Discord communities I'm part of, and plenty of other places. Sometimes I find something interesting while looking for something completely different. Other times, I go looking for something specific and end up finding absolutely nothing useful.
That's part of the process!
On average, I spend around an hour a day, or roughly 6 hours a week, discovering and keeping track of opportunities and resources.
When I find something interesting, I usually bookmark it and start collecting the details. I don't necessarily include it in the very next edition. Something I find on Monday might need a little more checking before I decide whether it belongs in Friday's edition.
And here's one decision I'm particularly proud of: I never announced a fixed publishing time!
I committed to Fridays, but not to a particular hour. Looking back, that was probably one of my more sensible decisions. I get to keep my Friday promise without racing against a specific publishing time. Good job, past me ๐
Not Every Interesting Link Makes It Into the Radar
Finding an opportunity is one thing. Deciding whether it's actually worth sharing is another.
There are 2 things I pay attention to.
1st, who can actually access it?
I want the Radar to be useful to as many people as possible, regardless of where they're based. So naturally, I look for globally open opportunities first. The only problem? They're not always that easy to find! If anyone knows where all the global opportunities are hiding, please let me know.
So, I also look for programs that accept applicants from multiple countries. And if I come across something that's limited to a particular country or location, I don't immediately send it to the "not for us" pile.
I take a closer look at what it offers. Is it a good learning experience? Does it give applicants a chance to work on something meaningful, build connections, gain experience, or open up other opportunities? Basically, is it worth someone's time and effort to apply?
If I feel the answer is yes, I'll consider including it.
I may not find something that everyone can apply to every week, but I do try to make sure there's something for readers in different parts of the world.
2nd, is it worth my reader's time?
Now, just because something has a fancy title or looks exciting on the surface doesn't mean it automatically makes it into the Radar.
I try to dig a little deeper and see what it's actually offering. What can someone gain from participating? Is there a chance to learn something, gain practical experience, build connections, or work on something interesting? And how much time and effort does it ask from applicants?
I also make sure to check the official sources for eligibility, deadlines, fees, and application details. Sometimes an opportunity looks fantastic when you first come across it, but after reading the details, you realize it's a completely different story. So, no judging a book by its cover here ๐
And then comes the question of paid opportunities!
I personally prefer free opportunities and try to include them as much as possible. There are so many people looking for ways to learn, grow, and gain experience, and I don't want application fees to become another barrier.
That doesn't mean I'll automatically skip every paid program. If something looks genuinely valuable, I'll take a closer look at what it offers and whether it's worth the fee. And if I include it, I'll make sure the cost is clearly mentioned. No unpleasant surprises!
And one more thing: I'm perfectly happy to publish an edition with fewer opportunities if I haven't found enough that I think are worth sharing. I'm not trying to win a competition for the longest list of links! I'd rather share 3 opportunities I'd recommend looking into than add 5 more just to make the edition look bigger.
The Friday Promise (25 Fridays and Counting!)
When I announced Dev Opportunity Radar, I said I'd be back every Friday.
And so far, I haven't missed a single Friday edition ๐
Now, before that sounds like I've had a perfectly organised six months, let me tell you that hasn't exactly been the case.
There have been weeks when research took longer than expected, weeks when I had other things going on, and times when life outside the Radar wasn't particularly easy. I even shared a little personal note in one of the editions because, well, life happens!
But somehow, I kept coming back to it. I enjoy discovering opportunities and putting these editions together, and I didn't want to give up something that had become such a meaningful part of my week.
Of course, I know consistency isn't always easy, and I don't think anyone should feel they have to push themselves to publish something every week at the expense of their well-being. If life gets in the way, that's okay too.
For me, this weekly commitment has been something I've enjoyed keeping. And knowing that some of you look forward to the Radar on Fridays makes me even happier to continue.
So, that's a little peek into what goes on before each edition reaches you. Not quite as simple as finding a few links, is it?
Okay, I'll put my serious hat back on now. We have a little more to talk about ๐
Giving the Radar a Home: A Little Special Announcement
Some of you might remember that I launched the Dev Opportunity Radar website on July 14, 2026, after publishing seven editions.
I won't go into all the details here since I've already shared the story behind building it in a separate article. The idea was to make it easier for readers to browse opportunities, revisit previous editions, explore Community Finds, and find things without having to go through multiple articles.
If you missed that announcement, you can read it here:
๐ I Finally Built the Dev Opportunity Radar Website โค๏ธ
But there's another little update I've been waiting to share properly!
Dev Opportunity Radar Now Has a .com Domain ๐
On October 2, 2026, I secured devopportunityradar.com!
Some of you might have already noticed the new domain in the links I've been sharing in recent editions. I've been quietly updating them, but I hadn't made a proper announcement yet. I wanted to save that for this milestone.
I know getting a domain might not sound like a big milestone, but this one means a lot to me.
Until then, I'd been using an .ai.studio domain. As the Radar grew, I started feeling that I wanted it to have its own identity and a proper home. I could have continued using the existing domain, but I wanted to take this little project a step further.
And honestly, I'm happy I did.
I've spent so much time working on Dev Opportunity Radar, from researching opportunities every week to building the website and maintaining it alongside the editions. What started as a simple idea has become something I've genuinely invested my time and effort in. Getting the .com domain felt like another way of committing to something I want to keep building.
There's a cost involved in maintaining a domain, of course, but I'm happy to take that on. This is something I care about, and having its own domain makes it feel a little more real to me. It's no longer just a weekly series I publish on DEV or a website I put together. It's something I'm building and hope to continue growing.
And just to be clear, the website isn't replacing the weekly editions. Both are staying! The articles will continue bringing you new opportunities and Community Finds every Friday, while the website makes it easier to explore what's already been shared.
I'm also grateful to everyone who has shared feedback and suggestions since the website launched. I've already made a few improvements based on what readers have suggested, and I hope to keep making it better.
So, if you haven't visited yet, here's the new home of Dev Opportunity Radar:
It's a small milestone in the bigger journey, but one I wanted to celebrate here ๐
A Few Things This Journey Has Taught Me
I don't think I have everything figured out after 25 editions. I'm still learning, trying things, and figuring out what works better.
But looking back, there are a few things I've come to appreciate about starting something, building it over time, and sharing it with a community.
You Don't Need to Have Everything Figured Out When You Start
When I published the first edition of Dev Opportunity Radar, I didn't have a website, a .com domain, or a clear idea of how the series would grow. I hadn't even figured out what every edition would look like.
I just had an idea I wanted to try, so I started with what I had.
The website came later, after I realized there was a way to make the collection more accessible. Other improvements happened along the way as I understood what the series needed.
I think sometimes we spend so much time planning what something should eventually become that we delay actually starting it. But you don't necessarily need to know the entire direction from day one. You can start small, learn as you go, and make changes when you have a better idea of what you want to build.
Let the People Using It Shape What It Becomes
One thing I didn't fully anticipate when starting Dev Opportunity Radar was how much the community would contribute to its growth.
The Community Finds section was part of the original idea, but seeing people actually send in opportunities, share feedback, and suggest improvements made me realize that a project doesn't always have to grow only in the direction you initially imagined.
For example, Klaudia suggested moving closed opportunities to the bottom of the website's listings. It was a simple suggestion, but it made the browsing experience better.
I think there's a difference between building something for people and actually involving them in the process. If you're creating something that others will use, leave room for their ideas and pay attention to how they interact with it. You might discover improvements or possibilities that you wouldn't have thought of yourself.
Don't Measure Everything by the Numbers
This is probably something I've had to remind myself of the most.
I'll be honest: the views might not always be as high as I'd hope. And I'd be lying if I said I never feel a little disappointed when I see the numbers.
But for Dev Opportunity Radar, my concern isn't simply getting more views. When I spend time finding and curating opportunities, I think about the people who might benefit from discovering them. So naturally, I sometimes wonder whether the series is reaching enough people.
At the same time, I don't know what happens after someone reads an edition. Someone might bookmark an opportunity, apply for a program, discover a new community, or find a resource they were looking for. I don't necessarily get to see any of that.
That's something I've come to understand: not every meaningful outcome is visible to the person creating something.
I also think it's important to remember that you can put a lot of effort into something and still have limitations. I'm one person, and I won't discover every opportunity. Manual research and curation take time, and not every opportunity will be relevant to every reader. That's okay.
What matters to me is that I'm making a genuine effort to share useful finds, verify the details, and give readers something worth exploring.
And if you enjoy creating something, don't let the numbers become the only reason you decide whether it's worth continuing. Pay attention to the people who find it useful, the things you learn while building it, and whether you still believe in what you're doing.
For me, those things matter just as much.
Okay, So What's Next? ๐
Well, first things first, Edition #26 is coming this Friday! So no, we're not stopping at 25 ๐
I don't have a big roadmap for the next 25 editions or a particular number I'm trying to reach. I want to keep finding opportunities worth sharing, welcoming your Community Finds, and making little improvements to the website whenever I can.
And please keep sending me things you've discovered! It doesn't have to be some huge opportunity or a well-known program. Sometimes a small event, an interesting community, or a resource you've found useful can be exactly what another reader needs.
I'm already looking forward to Edition #50. Imagine coming back here again and looking at everything that happened between #25 and #50. New opportunities, new contributors, new readers, and probably a few unexpected things along the way. Maybe we'll have another AMA too. Let's see ๐
I don't know what the next 25 editions will look like, but I'm excited to keep finding out. For now, I'll take it one Friday at a time.
25 editions down. 26 is already on its way. See you this Friday ๐
Ask Me Anything ๐
Since this is a little milestone article, I thought it would be a nice opportunity to open up a conversation.
If you've ever thought about starting a series on DEV, or you're curious about how I put Dev Opportunity Radar together, feel free to ask me anything.
You can ask about finding ideas, researching opportunities, deciding what to include, building a website alongside a series, staying consistent, getting started as a new writer, or anything else you're curious about.
I'm happy to share what has worked for me, what hasn't, and the things I'm still figuring out. I don't consider myself an expert at running a series, so everything I'll share comes from my own experience rather than a set of rules everyone should follow.
And if you're already running a series of your own, I'd love to hear from you too.
We're a community with people at different stages and with all kinds of experiences. Some of you might have been running a series for years, some might have just started, and others might be thinking about starting one.
You might have figured out a way to stay consistent, found a better way to research and organize your content, learned how to make your series more useful to readers, or discovered something that made managing it easier.
I'd love to hear about those experiences. Your advice might be exactly what someone else reading this has been looking for. And honestly, I can learn from it too. I'm still figuring things out, and I see this as a work in progress.
So, this isn't just an AMA where you ask me questions. It's also an opportunity for all of us to share what we've learned from running or following a series.
If you have a question, a suggestion, something you've learned, or even an experience you'd like to share, please leave it in the comments.
Let's make this a conversation where we can all learn something from each other ๐
Looking forward to chatting with you!
๐ Quick Links
| What | Link |
|---|---|
| Dev Opportunity Radar Website | devopportunityradar.com |
| Read the Editions | Browse the series on DEV |
| Website Launch Story | I Finally Built the Dev Opportunity Radar Website โค๏ธ |
๐ค Let's Stay Connected
| Place | Find me here |
|---|---|
| GitHub | building things โ hemapriya-kanagala |
| resources & updates โ hemapriya-kanagala | |
| X | random dev thoughts โ @KanagalaHema |










Top comments (21)
AMA starts here ๐
Since this is the 25th edition, I thought it would be a nice opportunity to have a little conversation with all of you! Whether you have questions about writing, finding ideas, building a series, engaging with the community, staying consistent, or anything else about my journey with Dev Opportunity Radar, I'd be happy to chat.
I will be around in the comments throughout the day, and I'd love to hear about your own journey too.
If you've been writing on DEV for a while, I'd love to hear any lessons, tips, or advice you've picked up along the way. And if you're thinking about starting your own series, feel free to share your questions as well.
Let's make the comments a place where we can all share our experiences and learn from each other. Looking forward to chatting with you ๐
How can I bag a paid internship as junior dev from Nigeria.
Congratulations didiโค๏ธ๐ฅฐ๐๐ป
Congrats @francistrdev sir too!โค๏ธ๐ฅ
Good work ๐ฅฐ
Julien Avezou (@javz)
Phinn Markson (@marsonp)
La Shara Cordero (@earlgreyhot1701d)
Konark Sharma (@konark_13)
Dhruv Jani (@dj29)
Boon (@hboon)
Thank you so much, Tara ๐โค๏ธ
Thanks Star!
@hemapriya_kanagala Di, its great!
Thanks for the mention and well I'm again in exam prep for SEM-7 starting next week. So, I'm kinda not into any other hacks since last 2 months due to hacktoberfest, diwali, exams and all so I stopped looking out for them.
BUT ...
HEY! Somebody started using GIFs, that's great!๐
It's totally fine, bhai! I can understand. All the best with your exam prep, and make sure to take care of yourself too ๐
about the GIFs, I'm actually not much of a GIF person, but I had a lot of fun adding them to this article! Francis (@francistrdev) had suggested using them a long time ago, so I had tried them in a few articles before stopping. I guess I found my GIF inspiration again for this article ๐
It does bring light into the articles since I do prefer seeing pictures time to time instead of just all text. Whatever works for you and thanks for the mention. Good work! :D
Thanks for suggesting it in the first place and for always supporting the Radar, Francis! I'll try to find more places to add them in future articles too ๐
Thanks Di,
And Have A Great Week!
You too, bhai! Have a great week ๐
25 editions is amazing! ๐
I really think this is such a valuable initiative, and your consistency is seriously impressive. Itโs not just a list of links either.
Youโre actually helping people discover opportunities they might otherwise miss, so this definitely feels worth continuing. ๐
The website looks really stylish too! ๐ธ
And I had no idea Cursor was looking for Ambassadors. That sounds interesting!
I honestly discover opportunities like that mostly through your Radar, which is one of the reasons I always enjoy checking it out. ๐
Congrats again on #25!
Thank you so much for always supporting the Radar, nyaomaru! I actually mentioned you in the article too; I hope you got the notification! And I'm really happy to hear that you've discovered opportunities through the Radar. That's exactly what I hoped for when I started this ๐
I saw the shoutout! ๐ธ๐
I was really happy to see my name there!!
I didnโt actually get a notification for it though. ๐น
But thank you so much for mentioning me, and keep going with the Radar! Iโm looking forward to seeing where it goes next. ๐
Congratulations on version 25!๐ And also on the further improvement of getting a .com domain! Rome wasn't built in a day. Good luck with future improvements too!
Hi Hemapriya,
I came across FR8 on Radar #2 and tried to apply on the same day itself.
Unfortunately they didnโt accept my application, but I would never have heard of the program if not for your list. Iโve also applied this month to the PayPal AI Hackathon.
Can you tell me how you determine whether African-based readers can apply to programs that have country limitations or on-site requirements?
Congratulations on a huge milestone, tbh devoppurtunity radar has been a revelation for me, it exposed me to oppurtunities I could only dream of thanks to Hemapriya, and I'm grateful for this. ๐๐๐Cheers to the 25th Edition, next stop 50th and beyond.
Congratulations on 25 editions, Hemapriya, and on not missing a single Friday! ๐ What stood out to me is how deliberately the Radar was built, more than the numbers themselves.
Leaving the Community Finds section empty in Edition #1 was a smart move. Most series add reader participation later, once they want engagement. You built the slot before anyone had used it, and it told readers you meant โour radarโ before you said it. Reader Updates is the natural next step. It closes the loop on โwhat happened after you found something?โ, which is the hardest part of curation to see. Danielโs FR8 application and Anhโs OpenAI Build Week submission are the kind of evidence that numbers canโt give you.
Your curation criteria are the real product. Anyone can aggregate links, and a search engine can do that. What you add is judgment:
You check the official source for eligibility, fees, and deadlines before sharing.
You ask what the applicant gains and how much time it costs them.
You state paid costs upfront.
Youโll publish fewer items rather than pad the list.
That is what lets a reader trust a link without checking it themselves, and itโs why a โ3 good opportunitiesโ edition can be worth more than a list of 8.
The โFriday, but no fixed hourโ decision is good advice for anyone starting a series. Commit to the cadence, not the clock. Your note that nobody should burn out for consistency matters too. Missing zero Fridays in 25 weeks is great, but a series that survives a bad week is better than one that is perfect for two months and then disappears.
On views vs. impact: I think youโre right to look past views, and you hint at why. Your outcomes happen off-platform, when someone bookmarks a link or applies to a program. A few ideas, if you ever want some signal without spoiling the project:
Add a โDid you apply to something from this edition?โ link or a short form to the website. Reader Updates then has an easy way in beyond the comments.
If the site has privacy-friendly analytics, track which listings get outbound clicks. That is closer to โdid this reach someoneโ than article views are.
Add a per-listing โI appliedโ or โthis helpedโ button. Itโs small, and it gives you a quiet outcome count.
Questions for the AMA:
With 6 hours a week of research, have you found a system for tracking opportunities by deadline and by stage (found, verifying, ready)? Iโm curious how you keep that from becoming a second job.
How do you handle opportunities that go stale or get cancelled after youโve published them? Does the website fix that better than the articles can?
Now that you have the site and the domain, are you thinking about things like email or RSS alerts for new listings, or do you want to keep Friday as the one rhythm?
Which section of an edition do you think readers use most: Community Finds, the opportunities, or the learning resources?
Also, I like that you grew the project in response to its users, like Klaudiaโs suggestion to push closed opportunities to the bottom. Those small changes show readers youโre paying attention, and that tends to bring in more contributions.
Looking forward to #26, and #50! ๐
Congratulations on hitting 25 editions of the Radar and launching your dedicated website!๐ I joined DEV on May 20. Just checked โ it turns out I liked the very first issue! What a lovely coincidence, hahaha.๐
Great to see how far this series has come! And very glad to have been here since the very beginning!
Thank you so much, Julien, for always being so supportive! And thanks for the Gem too ๐