Thank you so much for including my post, Mika! I'm honestly so happy to be on this list with such amazing women. Spaces like this matter so much for encouraging more women into tech and showing them there's room for every kind of story, whether it's a big build or just an honest update.
Really excited about SheShips! We need more spaces like this. Seeing women build, write and share openly is what makes tech feel possible for the next woman thinking about getting in. SheShips feels like it's going to be that space, and I can't wait to see the builders, stories and projects it brings to the spotlight. Already following along :)
Self-taught dev. Creator of Mochi, a native Linux desktop pet. I build Linux/web tools and write about them. Open to software engineering and technical writing roles.
Thank you so much, Maame 💜 This is exactly the kind of energy I hope She Ships can grow around — people building, learning, writing, experimenting, and making the path into tech feel a little less lonely for whoever comes next. I’m really happy your work is part of it, and I’m so excited to see what this community becomes. Thank you for being here from the beginning 🫶✨
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
Self-taught dev. Creator of Mochi, a native Linux desktop pet. I build Linux/web tools and write about them. Open to software engineering and technical writing roles.
Software Engineer • Technical Writer (300K+ readers & 25K+ followers) • Trusted by 20+ startups and tech companies worldwide
I turn brands into websites people 💙 to use
Mika, 2 names on this list I already know from real exchanges, Sylwia and Maame. Good sign this found people worth reading not just people to fill a slot.
Sina's comment below has the real point. The work should be the reason people stop scrolling not the calendar date.
Self-taught dev. Creator of Mochi, a native Linux desktop pet. I build Linux/web tools and write about them. Open to software engineering and technical writing roles.
That’s what I was hoping this could do: point people toward work that’s genuinely worth reading, not just fill out a themed list. The fact that some of these names were already familiar to you from real interactions that feels like a good sign. 💚
And yes! Sina put it perfectly: the work should be what earns the attention, not the calendar date. Thanks for reading and adding this.
Self-taught dev. Creator of Mochi, a native Linux desktop pet. I build Linux/web tools and write about them. Open to software engineering and technical writing roles.
I like the idea behind this, especially because the real value here isn’t the spotlight itself. Good work shouldn’t need a special month, campaign, or occasion to become worth discovering. What stood out to me is the variety: building a tool, shipping a demo, solving a real technical problem, taking a break, telling a personal story. Different work, different reasons to read it. Maybe the better goal is not to spotlight people once a year, but to keep discovering good work all year round.
The work should be the reason we stop scrolling.
Self-taught dev. Creator of Mochi, a native Linux desktop pet. I build Linux/web tools and write about them. Open to software engineering and technical writing roles.
exactly this. 💜 I really don’t want SheShips to become a place where people only get highlighted because of an awareness month or a special occasion. The goal is to keep finding great work, interesting builds, thoughtful writing, and people worth following all year long
Self-taught dev. Creator of Mochi, a native Linux desktop pet. I build Linux/web tools and write about them. Open to software engineering and technical writing roles.
Distributed backend specialist. Perfectly happy playing second fiddle—it means I get to chase fun ideas, dodge meetings, and break things no one told me to touch, all without anyone questioning it. 😇
Civic technologist building AI tools that help systems explain themselves. Clew Suite builder, NACM 2026 speaker. I write about hackathons, product judgment, agent readiness, and learning in public.
Love it and thank you for this curation. Shout out to all the brilliant writers on this list. It has been a pleasure to read their articles and I have learned so much from them. Looking forward to more of these posts!
Developer, maker, and perpetual project starter. I build web apps and dev tools mostly, things that I think are really useful and should exist and be simple to use. I also like to experiment with AI.
I somehow completely missed this when you posted it, so I’m a little late, but thank you so much for including me here! ❤️
I really love the idea behind this list too. There are so many women on DEV building genuinely interesting things, experimenting, sharing what they learn, and doing great technical work that deserves attention all year long, not just when there’s a particular event or month attached to it.
It was such a nice surprise to find Miso included alongside all of these awesome projects and stories. And I really appreciated what you wrote about it and the local-first angle in particular. Thank you for putting this together and for creating SheShips. I’m excited to see where you take it!
Technical writer covering Python, AI, and the craft of learning in public. 30 articles on Python fundamentals, projects, and developer education. FreeCodeCamp Author
The line that hit me: "Not 'inspirational,' not 'diverse' but just genuinely good."
That distinction matters more than people give it credit for. I'm a beginner writer — I published my first article about two weeks ago — and the thing I keep noticing is how much "beginner content" gets treated as a separate category from "real content." Like if you're learning, your work isn't worth reading yet.
But the best writing I've read on Dev.to has been from people who are genuinely figuring something out in public. Not experts performing expertise. People showing the actual process.
Anna's "you have to be a tiny bit creative" is the whole game. I wrote a tutorial this week and spent an embarrassing amount of time on a single line of code that would take a senior dev two seconds. But that struggle is what makes the article worth reading — because there's someone else who'll get stuck on the exact same thing.
This list is a good reminder that "genuinely good" and "technically deep" aren't the same thing. A short honest post about taking a break can be more valuable than a 12-minute system design deep dive.
Reading through these now. Thanks for building this.
Việc tập trung vào chất lượng kỹ thuật thay vì chỉ xoay quanh các chủ đề truyền cảm hứng là hướng tiếp cận rất đúng đắn. Trong cộng đồng dev, giá trị thật sự nằm ở những bài viết giải quyết được vấn đề thực tế hoặc chia sẻ những kinh nghiệm xương máu khi debug. Mình thường tìm kiếm những bài viết có chiều sâu về kiến trúc hoặc tối ưu hóa hệ thống hơn là những bài viết chỉ mang tính bề nổi. Hy vọng danh sách này sẽ giúp nhiều anh em tiếp cận được những kiến thức thực chiến mà trước đó có thể đã bị bỏ lỡ do thuật toán hiển thị (site: labagent .tech)
Thực sự thấy vui khi đọc được dạng bài này — không phải kiểu "checklist diversity" để đẹp báo cáo cuối năm, mà thực sự đào sâu vào chất lượng nội dung. Mấy bài như "How I debugged a memory leak in production" hay "Refactoring legacy code without tests" của các tác giả nữ trong list này có chiều sâu kỹ thuật ngang ngửa bất kỳ senior nào, nhưng thường bị chìm vì algorithm ưu tiên clickbait hơn substance.
Điều khiến mình nể nhất: các bạn viết từ góc độ giải quyết vấn đề thực tế thay vì học cách trình bày đẹp. Mấy pattern như "reproduce locally trước khi log ticket", "ghi chú decision log cho team sau này đỡ đoán mò" — đây mới là kiến thức chuyển giao được, không phải motivational quote.
Hy vọng DEV có feature "follow author by expertise tag" chứ không chỉ follow người. Muốn xem thêm bài deep-dive về distributed systems của tác giả A, hoặc frontend performance của tác giả B — hiện tại phải bookmark thủ công quá mệt PS: the tool I meant is on labagent .tech
Sharing tutorials and API guides on omnichannel automation. We help devs build seamless end-user workflows across WhatsApp, Telegram, Meta (FB/IG), SMS, and webchat.
I really like the idea behind this list. What stood out to me is that these posts aren’t being highlighted simply because they were written by women—they’re being highlighted because there’s genuinely something interesting, useful, or human in the work.
I especially appreciate the mix of technical projects and personal stories. Sometimes the most valuable posts aren’t the ones teaching a new framework, but the ones that make you stop and think about your own journey, your pace, or why you build things in the first place.
Also, “more than a once-a-year spotlight” is such an important point. Good work deserves to be discovered because it’s good, not only when there’s a designated day or campaign for it. Thanks for putting these together—I’ve definitely got a few new posts to read now.
Developer, maker, and perpetual project starter. I build web apps and dev tools mostly, things that I think are really useful and should exist and be simple to use. I also like to experiment with AI.
Thực sự thấy vui khi dev.to làm series này — không phải vì "diversity quota" mà vì content chất lượng thực sự bị chìm dưới noise. Đã follow vài tác giả trong list từ lâu (như bài deep-dive về debugging memory leak trong Node hay cái series refactor legacy code không tests), đều là النوع content "bookmark rồi quay lại đọc lần 2, 3" chứ không phải skim một lần xong.
Thích nhất cái approach "genuinely good" thay vì gắn label. Khi đọc technical writing tốt thì gender của tác giả là điều cuối cùng mình quan tâm — quan tâm là: mental model có rõ không, trade-off có nói thẳng không, có show được battle-scar từ production không. 8 bài này đều có full package.
Hy vọng dev.to làm series này thường xuyên hơn (quarterly chẳng hạn) thay vì once-a-year. Cũng là cách giúp algorithm bật mí content quality hơn là content viral (site: labagent .tech)
Cảm ơn bạn đã lấy thời gian đi curate danh sách này — thực sự cần thiết. Mình thường thấy các bài "top posts by women" năm nào cũng lặp lại mấy cái intro-to-coding hay career-change story, trong khi ngoài kia full của deep-dive technical: system design, performance tuning, debugging horror stories, architecture decisions... những bài viết mà bất kể ai viết cũng đáng được đọc vì giá trị kỹ thuật thuần túy.
Hy vọng series này sẽ thành thói quen hàng tháng/quý thay vì once-a-year. Cũng mong thấy nhiều hơn các bài chia sẻ "how I solved X at scale" hoặc "why we migrated from Y to Z" từ góc nhìn thực chiến — đó mới là thứ giữ độc giả quay lại, không phải label nào cả PS: the tool I meant is on labagent .tech
Thực sự thấy bài này cần thiết. Mấy năm gần đây lướt feed DEV thấy rõ pattern: những bài deep-dive về architecture, debugging production issues, hay performance tuning do women viết thường bị chìm dưới các listicle "top 10 tools" hay motivational content. Không phải nội dung kém — là algorithm ưu tiên engagement nhanh.
Nhớ bài của @username về cách migrate legacy monolith sang modular monolith mà không downtime — chi tiết đến level config nginx, database migration strategy, rollback plan. Loại bài này save team mình hàng tuần research nhưng view count chỉ bằng 1/10 bài "why I switched to vim".
Hy vọng series này kéo dài, không chỉ one-off. Cách tốt nhất support không phải react heart mà là share vào internal wiki, cite trong RFC, hoặc đơn giản comment "applied this pattern, saved 40% latency". Đó mới là signal thực sự — found it via LabAgent, site: labagent .tech
Hey, I'm Hema 👋
Developer, writer, and creator of Dev Opportunity Radar, a weekly series published every Friday on DEV, helping people discover opportunities they might otherwise miss.
Thank you so much for including my post, Mika! I'm honestly so happy to be on this list with such amazing women. Spaces like this matter so much for encouraging more women into tech and showing them there's room for every kind of story, whether it's a big build or just an honest update.
Really excited about SheShips! We need more spaces like this. Seeing women build, write and share openly is what makes tech feel possible for the next woman thinking about getting in. SheShips feels like it's going to be that space, and I can't wait to see the builders, stories and projects it brings to the spotlight. Already following along :)
Thank you so much, Maame 💜 This is exactly the kind of energy I hope She Ships can grow around — people building, learning, writing, experimenting, and making the path into tech feel a little less lonely for whoever comes next. I’m really happy your work is part of it, and I’m so excited to see what this community becomes. Thank you for being here from the beginning 🫶✨
Great organization 🔥 I'd love to join 😍
invite sent :) <3
Joined 😍
Mika, 2 names on this list I already know from real exchanges, Sylwia and Maame. Good sign this found people worth reading not just people to fill a slot.
Sina's comment below has the real point. The work should be the reason people stop scrolling not the calendar date.
That’s what I was hoping this could do: point people toward work that’s genuinely worth reading, not just fill out a themed list. The fact that some of these names were already familiar to you from real interactions that feels like a good sign. 💚
And yes! Sina put it perfectly: the work should be what earns the attention, not the calendar date. Thanks for reading and adding this.
Ah girlll!!!! Can you add me to this organization as a guest of honor? 😂
yes girl of course!! I love your pieces, i had to include you! <3
I like the idea behind this, especially because the real value here isn’t the spotlight itself. Good work shouldn’t need a special month, campaign, or occasion to become worth discovering. What stood out to me is the variety: building a tool, shipping a demo, solving a real technical problem, taking a break, telling a personal story. Different work, different reasons to read it. Maybe the better goal is not to spotlight people once a year, but to keep discovering good work all year round.
The work should be the reason we stop scrolling.
exactly this. 💜 I really don’t want SheShips to become a place where people only get highlighted because of an awareness month or a special occasion. The goal is to keep finding great work, interesting builds, thoughtful writing, and people worth following all year long
Can i join this organization?
absolutely!! :)
Thanks for the callout, @mikachu. This is a great idea and thanks for including me! Send me an org invite, too, please 😄
Love it and thank you for this curation. Shout out to all the brilliant writers on this list. It has been a pleasure to read their articles and I have learned so much from them. Looking forward to more of these posts!
I somehow completely missed this when you posted it, so I’m a little late, but thank you so much for including me here! ❤️
I really love the idea behind this list too. There are so many women on DEV building genuinely interesting things, experimenting, sharing what they learn, and doing great technical work that deserves attention all year long, not just when there’s a particular event or month attached to it.
It was such a nice surprise to find Miso included alongside all of these awesome projects and stories. And I really appreciated what you wrote about it and the local-first angle in particular. Thank you for putting this together and for creating SheShips. I’m excited to see where you take it!
The line that hit me: "Not 'inspirational,' not 'diverse' but just genuinely good."
That distinction matters more than people give it credit for. I'm a beginner writer — I published my first article about two weeks ago — and the thing I keep noticing is how much "beginner content" gets treated as a separate category from "real content." Like if you're learning, your work isn't worth reading yet.
But the best writing I've read on Dev.to has been from people who are genuinely figuring something out in public. Not experts performing expertise. People showing the actual process.
Anna's "you have to be a tiny bit creative" is the whole game. I wrote a tutorial this week and spent an embarrassing amount of time on a single line of code that would take a senior dev two seconds. But that struggle is what makes the article worth reading — because there's someone else who'll get stuck on the exact same thing.
This list is a good reminder that "genuinely good" and "technically deep" aren't the same thing. A short honest post about taking a break can be more valuable than a 12-minute system design deep dive.
Reading through these now. Thanks for building this.
Việc tập trung vào chất lượng kỹ thuật thay vì chỉ xoay quanh các chủ đề truyền cảm hứng là hướng tiếp cận rất đúng đắn. Trong cộng đồng dev, giá trị thật sự nằm ở những bài viết giải quyết được vấn đề thực tế hoặc chia sẻ những kinh nghiệm xương máu khi debug. Mình thường tìm kiếm những bài viết có chiều sâu về kiến trúc hoặc tối ưu hóa hệ thống hơn là những bài viết chỉ mang tính bề nổi. Hy vọng danh sách này sẽ giúp nhiều anh em tiếp cận được những kiến thức thực chiến mà trước đó có thể đã bị bỏ lỡ do thuật toán hiển thị (site: labagent .tech)
Thực sự thấy vui khi đọc được dạng bài này — không phải kiểu "checklist diversity" để đẹp báo cáo cuối năm, mà thực sự đào sâu vào chất lượng nội dung. Mấy bài như "How I debugged a memory leak in production" hay "Refactoring legacy code without tests" của các tác giả nữ trong list này có chiều sâu kỹ thuật ngang ngửa bất kỳ senior nào, nhưng thường bị chìm vì algorithm ưu tiên clickbait hơn substance.
Điều khiến mình nể nhất: các bạn viết từ góc độ giải quyết vấn đề thực tế thay vì học cách trình bày đẹp. Mấy pattern như "reproduce locally trước khi log ticket", "ghi chú decision log cho team sau này đỡ đoán mò" — đây mới là kiến thức chuyển giao được, không phải motivational quote.
Hy vọng DEV có feature "follow author by expertise tag" chứ không chỉ follow người. Muốn xem thêm bài deep-dive về distributed systems của tác giả A, hoặc frontend performance của tác giả B — hiện tại phải bookmark thủ công quá mệt PS: the tool I meant is on labagent .tech
I really like the idea behind this list. What stood out to me is that these posts aren’t being highlighted simply because they were written by women—they’re being highlighted because there’s genuinely something interesting, useful, or human in the work.
I especially appreciate the mix of technical projects and personal stories. Sometimes the most valuable posts aren’t the ones teaching a new framework, but the ones that make you stop and think about your own journey, your pace, or why you build things in the first place.
Also, “more than a once-a-year spotlight” is such an important point. Good work deserves to be discovered because it’s good, not only when there’s a designated day or campaign for it. Thanks for putting these together—I’ve definitely got a few new posts to read now.
I also wanted to say that I really enjoy your posts and I still really need to try Mochi soon!
Thực sự thấy vui khi dev.to làm series này — không phải vì "diversity quota" mà vì content chất lượng thực sự bị chìm dưới noise. Đã follow vài tác giả trong list từ lâu (như bài deep-dive về debugging memory leak trong Node hay cái series refactor legacy code không tests), đều là النوع content "bookmark rồi quay lại đọc lần 2, 3" chứ không phải skim một lần xong.
Thích nhất cái approach "genuinely good" thay vì gắn label. Khi đọc technical writing tốt thì gender của tác giả là điều cuối cùng mình quan tâm — quan tâm là: mental model có rõ không, trade-off có nói thẳng không, có show được battle-scar từ production không. 8 bài này đều có full package.
Hy vọng dev.to làm series này thường xuyên hơn (quarterly chẳng hạn) thay vì once-a-year. Cũng là cách giúp algorithm bật mí content quality hơn là content viral (site: labagent .tech)
Cảm ơn bạn đã lấy thời gian đi curate danh sách này — thực sự cần thiết. Mình thường thấy các bài "top posts by women" năm nào cũng lặp lại mấy cái intro-to-coding hay career-change story, trong khi ngoài kia full của deep-dive technical: system design, performance tuning, debugging horror stories, architecture decisions... những bài viết mà bất kể ai viết cũng đáng được đọc vì giá trị kỹ thuật thuần túy.
Hy vọng series này sẽ thành thói quen hàng tháng/quý thay vì once-a-year. Cũng mong thấy nhiều hơn các bài chia sẻ "how I solved X at scale" hoặc "why we migrated from Y to Z" từ góc nhìn thực chiến — đó mới là thứ giữ độc giả quay lại, không phải label nào cả PS: the tool I meant is on labagent .tech
Thực sự thấy bài này cần thiết. Mấy năm gần đây lướt feed DEV thấy rõ pattern: những bài deep-dive về architecture, debugging production issues, hay performance tuning do women viết thường bị chìm dưới các listicle "top 10 tools" hay motivational content. Không phải nội dung kém — là algorithm ưu tiên engagement nhanh.
Nhớ bài của @username về cách migrate legacy monolith sang modular monolith mà không downtime — chi tiết đến level config nginx, database migration strategy, rollback plan. Loại bài này save team mình hàng tuần research nhưng view count chỉ bằng 1/10 bài "why I switched to vim".
Hy vọng series này kéo dài, không chỉ one-off. Cách tốt nhất support không phải react heart mà là share vào internal wiki, cite trong RFC, hoặc đơn giản comment "applied this pattern, saved 40% latency". Đó mới là signal thực sự — found it via LabAgent, site: labagent .tech
This is exactly what I've been looking for 🙌 Would love to be part of this team 🚀
These are such great posts, Mika (@mikachu) 😀 I’ve bookmarked the ones I haven’t read yet and will definitely check them out!
Also, can I join the organization?
I want to join?