📌 TL;DR
Three months ago, I decided to start writing consistently on DEV. Twenty-five articles later, I've learned far more than how to write better.
I've learned that writing is much more enjoyable when you stop chasing numbers, that some of the best conversations begin in the comments, and that finding your voice takes time. More than anything, I've learned that the topics you're most connected to often become the ones only you can write.
If you're new to DEV, or if you're simply curious about my journey, consider this an open Ask Me Anything. Whether you have questions about writing, finding ideas, building a series, engaging with the community, overcoming challenges, or anything else related to your own journey on DEV, I'd be happy to chat.
I definitely don't have all the answers, but if anything I've learned over the past three months can help you in any way, I'd love to share what I know. So feel free to ask me anything in the comments.
Table of Contents
- Why I Wanted to Write This
- From Silent Reader to Writer
- Lesson 1: Write Because You Enjoy It
- Lesson 2: Comment More Than You Think You Should
- Lesson 3: Don't Let Numbers Define Your Journey
- Lesson 4: Your Voice Will Change
- Lesson 5: Write What You Can Relate To
- Lesson 6: Community Makes Ideas Better
- Lesson 7: It's Okay to Take a Break
- Final Thoughts
- Ask Me Anything 💙
- 🤝 Let's Stay Connected
Why I Wanted to Write This
When I sat down to write this article, I realized it had been almost three months since I started writing consistently on DEV. During that time, I've published 25 articles, and this one makes 26. It's honestly hard to believe how much has happened in such a short time.
I was fortunate enough to have two articles featured in the Top 7, start a series called Dev Opportunity Radar, and eventually launch a website for it. Those are milestones I'm incredibly grateful for, but when I think about these past three months, they aren't the first things that come to mind.
What I remember most are the people. The conversations in the comments, the encouragement when I doubted myself, the community members who shared opportunities that became part of Dev Opportunity Radar, and the readers who reached out to tell me an article helped them or introduced them to something they might have otherwise missed. Those moments have meant more to me than any number ever could.
I don't consider myself an expert. Three months is only a small part of what I hope will be a much longer journey. But these past few months have taught me lessons I wish someone had shared with me when I first started writing. I hope they help someone who's just beginning their own.
From Silent Reader to Writer
When I first joined DEV, I spent much more time reading than writing. I'd browse articles, learn from discussions, and admire the people who confidently shared their experiences and ideas. At the same time, I wasn't sure if I had anything meaningful to contribute myself, so for a long time I stayed a quiet reader.
I don't think there's anything wrong with that. Every community has people who learn by listening before they feel ready to join the conversation, and I was definitely one of them. Eventually, though, I started leaving comments. Then I shared a few thoughts of my own. Little by little, writing didn't feel quite as intimidating anymore.
English isn't my first language, and even today I still reread my articles wondering if I've explained something clearly enough or whether I've made a mistake. That self-doubt hasn't completely disappeared, and honestly, I don't know if it ever will. What's changed is that I've become a little more comfortable pressing Publish anyway, trusting that every article is another chance to learn and improve.
If I'd waited until I felt completely confident, I probably would have never written that first article at all.
Lesson 1: Write Because You Enjoy It
If there's one lesson that stands out above all the others, it's this: write because you genuinely enjoy writing.
When I first started, my mood on a given day often depended on how an article was doing. I'd refresh and check my views, reactions, and comments more than I probably should have. I think that's completely normal, especially when you're putting something you've worked hard on out into the world. We all hope people will read it and connect with it.
Over time, though, my perspective started to change. I realized that if I only felt happy when an article performed well, I was giving too much control over my enjoyment to something I couldn't control. Views are wonderful. Reactions are wonderful. Being featured is wonderful. I'm incredibly grateful for every single one of those things, but they've become a bonus rather than the reason I write.
Today, when an idea pops into my head, the first question I ask myself isn't, "Will this get a lot of views?" It's, "Is this something I'm excited to write about?" If the answer is yes, I usually end up enjoying the entire process, from researching and writing to reading the conversations that follow.
The articles I'm proudest of aren't always the ones that reached the most people. They're the ones I enjoyed creating, because those are the ones that feel the most like me.
Lesson 2: Comment More Than You Think You Should
If I could only give one piece of advice to someone who's new to DEV, it would be this: don't just write. Read. Comment. Join the conversation.
When I first started becoming more active here, I thought publishing articles would be the biggest part of my journey. Looking back, I don't think that was true. Some of my favorite memories didn't begin when I clicked Publish. They began in the comments.
Over the past three months, I've discovered incredible writers through comment sections, had conversations that made me think differently, and met people I never would have known otherwise. Some of those conversations even inspired future articles, while others introduced me to opportunities, ideas, and perspectives I probably wouldn't have found on my own.
Commenting has also changed the way I read. Instead of quickly scrolling to the next article, I spend more time thinking about what the author is trying to say. If something resonates with me, I try to tell them why. If I learn something new, I let them know. Sometimes it's a simple thank you, and other times it turns into a conversation that continues long after the article itself.
It's easy to think of DEV as a place where people publish articles, but to me it's much more than that. It's a community where people encourage one another, share ideas, celebrate wins, and learn together.
If you're just getting started, don't worry about writing the perfect article on day one. Start by reading what others are sharing. Leave thoughtful comments. Ask questions. Celebrate someone's achievement. Share your perspective when you have something to add. You never know where a single conversation might lead.
Writing brought me to DEV, but the conversations are what made me feel like I belonged here.
Lesson 3: Don't Let Numbers Define Your Journey
Every notification used to feel exciting, and honestly, every time an article didn't perform the way I'd hoped, it was hard not to wonder what I could have done differently. Looking back, I was checking my stats way more than they deserved. I think that's something many of us experience when we start sharing our work publicly.
Over time, though, I realized I was comparing my beginning to someone else's journey. Some writers have been part of the community for years. Some have built an audience over a long period of time. Others have found a niche they're known for. It's not really a fair comparison because everyone's path looks different.
I also realized that numbers don't tell the whole story. An article with fewer views might spark an amazing discussion. A single comment from someone saying your article helped them can mean more than hundreds of extra reactions. Some of my favorite articles haven't necessarily been my most popular ones, and that's completely okay.
These days, I still look at my article stats because I think it's natural to be curious, but they no longer decide whether I consider an article a success. What matters more is whether I enjoyed writing it, whether I learned something through the process, and whether it started a meaningful conversation.
One example of this for me is Dev Opportunity Radar. When I first started the series, I'll admit I hoped it would reach more people than it has so far. There are weeks where I wish it had more views because I believe these opportunities could help more developers. Maybe there are things I can improve, and I'm always trying to learn.
But I've realized something more important: I can't let those numbers decide whether I keep showing up every Friday.
I started Dev Opportunity Radar because I kept discovering amazing fellowships, grants, hackathons, and resources after it was already too late to apply. I didn't want other people to miss those opportunities for the same reason. That purpose hasn't changed just because a particular edition gets fewer views than I hoped.
What's interesting is that the numbers only tell part of the story. If you only looked at the view count, you might think the series isn't doing particularly well. But when I read the comments, it's a completely different picture. People share opportunities I would have never found on my own. They celebrate getting accepted into programs. They suggest improvements, contribute Community Finds, and tell me an edition helped them discover something they would have otherwise missed.
That reminds me that impact isn't always measured by views or reactions. Sometimes it's measured by the conversations you start and the people you help, even when those numbers aren't immediately visible.
Dev Opportunity Radar has changed me more than I expected.
It gave me a reason to show up every Friday and helped me find a place in the community that feels uniquely my own.
Even if only a handful of people read each edition, that's still a handful of people I have the chance to help, and to me, that's reason enough to keep going.
Lesson 4: Your Voice Will Change
One of the biggest misconceptions I had when I started writing was that I needed to figure out my writing style before I could become a consistent writer. I don't think that's how it works at all.
I think you discover your voice by writing. Every article teaches you something new about how you think, what you enjoy writing about, and how you connect with readers. As you keep writing, your confidence grows, your ideas become clearer, and you slowly begin to understand what feels authentic to you.
When I look back at some of my earlier articles, I can already see changes in the way I write. Some things I'd explain differently today, and there are ideas I'd probably approach from a different angle. I don't see that as a bad thing. If anything, it's a sign that I'm learning.
Even today, I don't think I've found my final writing voice, and honestly, I hope I never fully do. I hope it continues to evolve as I learn new things, meet new people, and gain new experiences. To me, that's one of the most exciting parts of writing. Every article becomes another small step in that journey.
So if you're just starting out, don't put too much pressure on yourself to find your "voice" before you begin. Start writing, keep showing up, and give yourself permission to grow. You might be surprised by how much your writing changes a few months from now.
Lesson 5: Write What You Can Relate To
The articles I've enjoyed writing the most all have one thing in common. They came from experiences I could genuinely relate to.
Dev Opportunity Radar is the clearest example. As I mentioned earlier, it grew out of a frustration I'd lived through myself: missing opportunities simply because I found out about them too late. The opportunity itself was rarely the problem. Access to information was.
That experience made me wonder how many other people were missing opportunities for the exact same reason. So I decided to start sharing the fellowships, grants, hackathons, and resources I came across each week, hoping someone else would discover them while there was still time to apply.
It taught me something I keep coming back to. The articles people connect with the most aren't always about the most popular topics. They're often the ones that come from experiences only you have lived, because those experiences give you a perspective nobody else can write in quite the same way.
If I could give one more piece of advice, it would be this: don't spend too much time trying to figure out what everyone else wants you to write. Instead, think about the experiences you've had, the challenges you've faced, the things you've learned, or even the problems you've wished someone had solved for you. Sometimes the best ideas come from asking yourself, "What do I wish I had known a year ago?"
That's still the reason I enjoy putting Dev Opportunity Radar together every Friday. The purpose has always been bigger than the numbers.
Lesson 6: Community Makes Ideas Better
One of the biggest surprises over the past three months is realizing that writing isn't really a solo activity. Every article may begin with one person behind a keyboard, but it rarely ends there.
Every time I press Publish, the article becomes something more because of the people who take the time to read it. Their comments make me think differently. Their questions inspire future articles. Sometimes they share their own experiences, and I end up learning just as much from them as they do from me. That's one of my favorite parts of writing on DEV: every article becomes the beginning of a conversation rather than the end of one.
Dev Opportunity Radar is probably the best example of this. I may be the one putting each edition together, but the series has never really felt like something I build alone. Community Finds was there from the very first edition because I wanted it to be a space where everyone could share opportunities, not just me. Since then, people have continued contributing opportunities I would've otherwise missed, Reader Updates have given people a chance to celebrate their own milestones, and the series has even grown into its own website. It no longer feels like just my series.
It's become something the community helps build every week, and much bigger than I could have built on my own.
Being part of that has changed me in ways I never expected. It's introduced me to incredible people and given me a place in this community that feels uniquely my own.
More than anything else, these past three months have reminded me that communities grow because people choose to contribute in their own way. Some write articles. Some leave thoughtful comments. Some answer questions, share opportunities, or simply encourage someone who's just getting started. Every one of those contributions matters, and together they create the kind of community people want to come back to.
A few people deserve a special mention here. @webdeveloperhyper, @klaudiagrz, @francistrdev, @javz, @technogamerz, @xulingfeng, @csm18, @itsugo and @shubhradev, thank you for always supporting me. On so many of my posts, you show up with a reaction or a comment, and it means a lot every single time. You've become friends at this point, and I always look forward to seeing you around the community.
I know I won't be able to name everyone who's supported me, and there are honestly so many more people who've been part of this in ways big and small. If I've missed your name, please don't take it personally. It's not intentional, and I'm just as grateful to you as to anyone I've named.
And to everyone else who's followed along and kept supporting my work, thank you. Whether you follow me here on DEV, read one article or all 25, left a comment, hit react, or simply read quietly without saying a word, that support means just as much to me. A reaction on a day I wasn't sure about an article has meant just as much as a comment or a message. You've helped shape my experience on DEV far more than you probably realize.
Lesson 7: It's Okay to Take a Break
One thing I've learned over the past three months is that it's okay to take a step back every now and then.
Last week was actually the first week in a while where I didn't publish a new article, apart from Dev Opportunity Radar. It wasn't because I had run out of ideas or because I didn't want to write.
I simply didn't have a topic that I genuinely felt excited about, and I didn't want to force one just for the sake of staying consistent.
If you're just getting started, I do think it helps to have a gentle goal. Maybe that's one article a week or even one every couple of weeks. Having a small target can help you build a routine without making writing feel like another obligation.
That said, I don't think every goal has to be followed perfectly. I usually aim to publish one article a week (apart from Dev Opportunity Radar), but if I don't have an idea that genuinely excites me, I'd rather wait than force something just to stay on schedule. In my experience, the more you write, read, and interact with the community, the more ideas naturally start to appear.
I think there's a lot of pressure online to always be creating, always publishing, and always staying visible. For me, writing has always been something I look forward to, and I'd like to keep it that way.
At the end of the day, we're all human. The hobbies, passions, and projects we care about shouldn't become another source of burnout. If taking a short break means coming back with more excitement and fresh ideas, that's a much healthier approach than forcing yourself to create something your heart isn't really in.
Final Thoughts
Three months ago, I simply wanted to become a better writer. I realize now I gained much more than that.
I became a little more confident every time I pressed Publish, discovered topics I genuinely enjoy writing about, found a community that constantly inspires me, and watched a small idea born from one of my own frustrations grow into something much bigger than I ever imagined.
If there's one thing these past three months have taught me, it's that writing is about so much more than publishing articles. It's about sharing experiences, learning from one another, and becoming part of a community where people genuinely want to see each other succeed. Some of the best parts of this journey didn't begin when I clicked Publish. They began when someone replied, shared their perspective, or simply started a conversation.
I don't know what the next three months will look like, and I hope they surprise me just as much as the last three have. I'm sure my writing will continue to evolve, my interests will change, and hopefully I'll keep finding new ways to contribute to this amazing community.
For now, I'm simply grateful that I decided to press Publish on that first article.
Ask Me Anything 💙
If you've made it this far, thank you so much for reading. Writing these articles has taught me a lot, but one of my favorite parts has always been the conversations that happen after I press Publish, so it felt fitting to end this reflection with a conversation too.
Everything I've shared here simply comes from my own experiences over the past few months, and I'm sure there's plenty I still have to learn. So if you're new to DEV, thinking about writing your first article, curious about Dev Opportunity Radar, or even feeling a little nervous about pressing Publish for the first time, feel free to ask me anything. Writing, finding ideas, building a series, engaging with the community, or anything else on your mind. If I know the answer, I'll share it. If I don't, I'll be honest about that too.
I'd also love to hear about your own journey. A lesson you've learned, a tip that's helped you, or something you're excited or nervous about if you're just starting out.
My hope is that the comments become more than a Q&A between you and me, a place where everyone shares stories and lessons that might help someone else just beginning their own.
I'm looking forward to chatting with all of you down there 💙
🤝 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)
Hey Hemapriya! I am glad that you have accomplished in the last 3 months and we are grateful for you that you continue to stay here on DEV.
I will add your article to the guide for others to look into. I think your time here on DEV and your lessons you have learned could reinforce other new users, especially lessons 1 and 2 (which I think is heavily important).
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! 💡
Francis, it means a lot that you'd include it in your beginner's guide. If it helps even one new writer feel a little more confident about pressing Publish, that'll make me incredibly happy.
I also remembered your suggestion from a while back about adding GIFs and images to articles, so I decided to give it a try this time. I actually think they made the article much more engaging and gave readers little pauses between sections. It definitely took me a while to find ones that matched the tone, but I had a lot of fun experimenting with it.
I've also removed the AI transparency note 👍
And thank you again for always being so supportive. Your encouragement and advice have helped me throughout these past few months, and I really appreciate it 😀
I am glad to see your GIF on your article as well! Brings light and engagement while reading :D
And for sure no problem! I am glad you are still here! If anything, feel free to ping if anything :)
I've actually applied to a few of your radar posts. Thank you very much for them!
A few things I've learnt from my side (I've been here for about 2 months now).
1, the numbers are wrong... If you create an account and post immediately, you'll get next to 0 views. Due to how Forem's internal DB operates. You get a trust score, based on activity, so the first week or 2 on the platform, you have a negative stat to your recommendation to people.
2, the numbers stay wrong... Once you catch traction, you'll see a sudden influx, 100 new followers, 300 new followers, in a single day. Those are bots, it translates to maybe 10 or 30 real people.
3, comments are king. Dont worry too much about posting, live in the comments a bit, it's honestly the most fun part of the platform.
4, dont rush.. You feel like you caught momentum, need to keep it going.. Stop, rest, relax, rather post when you got time and really want to post, rather than staying up to 3am just so you can do your daily post.
5, the community is 99% solid. There's a few people who are rude, regrading, overall just bad people on here... But the majority are bomb and you'll have fun chatting and having thoughtful conversations that might send you down a rabbit hole.
First of all, I'm really glad to hear you've applied to a few opportunities through Dev Opportunity Radar! That makes all the time that goes into putting it together feel worthwhile.
And thank you for sharing these lessons! I actually didn't know about the trust score and how it can affect visibility for new accounts, so that was really interesting to learn.
I completely agree with your points about comments and not rushing. Some of my favorite moments on DEV have come from conversations in the comments rather than publishing an article, and taking a short break this past week reminded me that it's much better to write because you're excited about an idea than to force yourself to keep a streak going.
I've had a really positive experience with the community too. Everyone I've interacted with has been incredibly kind and welcoming, and it's one of the biggest reasons I've enjoyed being here.
Thanks for taking the time to share your experience. I hope it helps someone else who's just getting started as well 💙
Same here, community has been awesome. But earlier today I saw 2 people bullying a poster because he used AI for his project and for writing up his post. That really ticked me off, because I know it takes 1 bad actor to discourage them from ever writing a post again. So I told them off, said they should bugger off to X or Reddit, they'd be welcomed there, here we prefer constructive commentary and friendliness. Not toxic anti-ai... I hope people atleast look past those outliers, the majority of people here have been absolutely incredible and I've had pretty much an all good experience.
I know what you mean. It only takes one bad interaction to make someone question whether they should post again, especially when they're new.
I'm glad you spoke up for them. Constructive feedback is one thing, but everyone deserves to be treated with respect.
Honestly, I didn't even realize this was happening. My own experience has been nothing but positive. I've received constructive criticism too, but it's always been kind, respectful, and genuinely helpful. I really hope new writers get to experience that side of the community, because it's been one of my favorite things about being on DEV 💙
Same, I've had constructive criticism, on my first post no less... I was called out on my documentation, said my benchmarks need to be far more granular and that's stuck with me, now my benchmarks are 2 pages long and track every stage of processing, which actually helped me develop better, by isolating the bottlenecks based on where the benchmarks are slow. But when I saw them be mean like that, I just couldnt stand it, I reported them and I told them off, cuz we all deserve a safe-space and I like to think Dev.to is that safe-space, where you can share what you've done and get positive feedback for it. Cuz developers are generally shy, or lack peers to share their thoughts with, so if someone makes a post, they're already stretched out on a limb, it takes 1 comment to make them disappear forever and write Dev.to off as another Reddit/X, where it's just a cesspool of insults and belittling. While everyone I've met has tried to keep it a productive, constructive place.
I completely agree with that. I think a lot of us already have so many doubts before we even hit Publish for the first time. It takes a fair bit of courage to put something you've worked on out there, especially when you're new. I can definitely see how one unnecessarily harsh comment could make someone decide not to post again.
That's why I'm really glad people like you speak up when they see it. I hope DEV continues to be the kind of place where new writers feel comfortable sharing their work and learning along the way.
Oh, forgot... 6, That red tag by your notifications will get you every single time...
That one is so true 😂
Even now, I still click that little red notification badge almost immediately whenever I see it. I don't think that excitement ever really goes away, and honestly, I hope it doesn't 😄
Right? @xulingfeng always falls for it 🤣
I feel a little better knowing I'm not the only one 😄
Oh and @xulingfeng hates it so much when I catch him 😂
I totally agree with the point about not chasing the numbers. 🙂
I've had some articles that were incredibly "clickable" and got far more views than anything else I've written. But honestly, some of my more mature, in-depth articles have meant much more to me—and I think they've provided more value to the community as well, even if they naturally attracted a smaller audience.
Views are nice, but they're not the best measure of impact.
Sylwia, I couldn't agree more 😀
I think that's something it took me a little while to realize too. At first it's so easy to focus on the numbers, but over time I've found myself caring much more about the conversations an article starts and whether it helped someone.
I really like how you put it: "Views are nice, but they're not the best measure of impact." I think that's a reminder all of us need from time to time 💙
Hey Hemapriya! Nice to hear from you.
I immediately say the value of your posts and your willingness to share with the community, so I am happy to be supporting since your first posts!
Really nice to see your growth here on DEV. Keep it up!
Julien, thank you! It really means a lot coming from someone who's been supporting Dev Opportunity Radar since the very beginning.
You've been one of the first people encouraging me to keep going, and I'm really grateful for that. Seeing familiar names like yours every week genuinely motivates me to keep putting the series together. Thank you for being part of the journey 💙
AMA starts here 💙
Whether you have questions about writing, finding ideas, building a series, engaging with the community, overcoming challenges, or anything else related to your own journey on DEV, I'd be happy to chat.
I'll 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 especially love to hear any lessons, tips, or advice you've learned along the way. Your experience might be exactly what someone who's just starting their writing journey needs to hear.
Let's make the comments a place where we can all learn from each other 😀
Wow, what a beautiful journey this is! ❤️
This article was not just about completing 25 articles, it was about the transformation from a silent reader to a confident writer. And honestly, that journey is truly inspiring.
Many people come to DEV, read amazing articles, learn from others, and think about sharing their own thoughts someday. But taking that first step and continuing consistently is where the real growth begins. You did exactly that, and it’s amazing to see how much you have achieved in just 3 months.
What I loved most is that your writing is not just about sharing knowledge; it carries your experiences, emotions, and the lessons you learned along the way. Every article feels like a small piece of your journey, and that is what makes writing truly meaningful.
25 articles in 3 months is not just a number — it shows your dedication, curiosity, and the courage to keep showing up.
And by the way, you are an amazing writer. The way you write such beautiful and heartfelt articles is truly special. Your words have a warmth that makes readers feel connected, and that is a rare quality.❤️
Thank you for sharing your journey with the community. Your story will definitely inspire many silent readers to finally start sharing their own voices.🔥
Congratulations on this wonderful milestone! Keep writing, keep learning, and keep inspiring. Looking forward to reading many more beautiful articles from you. ❤️
Divyanshi, thank you so much ❤️
I'm really happy that the article came across the way I hoped it would. More than celebrating 25 articles, I wanted to share everything I learned along the way, especially for people who are still thinking about writing their first post.
Your kind words about my writing honestly mean a lot. And thank you for being one of the people who's been supporting my journey for such a long time now. Seeing familiar names like yours in the comments has always been encouraging.
I really appreciate you taking the time to read the article and leave such a thoughtful comment. It means more than you know 💙