Leave a comment below to introduce yourself! You can talk about what brought you here, what you're learning, or just a fun fact about
yourself.Reply to someone's comment, either with a question or just a hello. š
Come back next week to greet our new members so you can one day earn our Warm Welcome Badge!
Top comments (570)
Welcome everyone to DEV! We are glad you decide to join us!
As mention before for many welcome threads before me, I will make my introduction at Welcome Thread v400! I made a promise to @javz that I will do this (though forgot the reason why lol).
In the meantime, feel free to visit my guide on dev.to!
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! š”
I will see you all next week there! In the meantime, what brings you to DEV?
Looking forward to your intro @francistrdev !
It's almost time already! šæ
I'm debating if I should make it short and sweet or a whole research article length lol
Hey! š Nice to connect with you. What technologies or projects are you currently working on? Always great to learn from fellow developers!
Hey Paresh! Just working on Next.js mostly. What about you?
Thank you for the warm welcome!
I'm excited to be part of the DEV community and looking forward to learning, sharing my experiences, and connecting with developers from around the world.
I'll definitely check out your guide. Looking forward to your introduction in Welcome Thread v400!
Hey Zeenathul Surfa Sahth, My Name is Farhan khan & I am fullstack developer I would like to connect techie people and build network . I am first year dropped student I desined my own path because I don't like tradational path
Thanks for the welcome, Francis! What brings me here is mobile deep linking, mostly. A lot of teams are still sorting out life after Firebase Dynamic Links, and I'd like to help where I can. Thanks for the guide link too.
Thanks Ying and hope the guide helps :)
Hey FrancisTRdev. My name is Hassan Ali I build free browsing tools people also enjoy using. Play Spacebar Clicker started as a small side project just a simple way to test how fast you can tap the spacebar and grew into free click tests, counters, and speed challenges.
playspacebarclicker.com/
heyyy
hiiii
hiiiii
hello and thanks for having me
Hello! I'm Tomasz, a Principal Software Engineer with 15y+ experience in JVM, and a conference speaker (3x at Devoxx Poland + a couple of smaller conferences). I have always loved building software that stands the test of time, which other developers love to work with. Today I'm exploring, how to do it in the agentic world by developing a couple of personal projects.
I joined dev.to to connect with other developers, find inspiration and to share a couple of my own thoughts and projects. Hope to bring something valuable to the community!
Hobby? Long-distance walking and cycling. Today the family redefined the meaning of "long", but a couple of years ago I walked half of Europe on foot in 4 months.
hi
hello.
pleased to be here
hi every one
Hey, looking forward to learn exciting things and share my thoughts with you all
hello, and thanks for welcoming me, nice to see there a lot of people here !
Hi! New here. I enjoy reading about product and interface design for apps with agents, and I plan to share a few notes in Portuguese too. Glad to join the community.
helloošš»
Hello!
Hi, Nice to connect with you.
Welcome welcome everyone!
Hi, I'm Guillermo, Head of Technology at Werk. We're building an AI assistant that keeps the work of teams on the move organized from their voice notes and photos. I'll be writing about model-agnostic harnesses, LLM routing and testing agents. Happy to be here.
Welcome Guillermo! LLM routing is very relevant to me. I run most of PostKing's generation through OpenRouter and send Claude calls direct. The biggest lesson so far: the same prompt doesn't behave the same across models. One model left reasoning on by default and quietly cut our blog posts short; another sometimes returns stray string fragments inside a JSON array. Do your harnesses validate each item, or do you retry the whole call? Following for the testing posts.
Hello
Hello! Your work sounds really cool!
Hey @francistrdev š
I'm Divyansh, and I'm exploring how technology works behind the scenes, especially in the world of AI and software engineering.
Lately, I've been spending a lot of time learning about LLMs, RAG, AI agents, embeddings, and how these technologies are being used to solve real-world problems.
I enjoy breaking down complex technical concepts into simple, practical explanations that are easy to understand, whether you're a beginner or an experienced developer.
I'm here to learn from the community, share what I discover, exchange ideas, and connect with people who are equally curious about technology.
Looking forward to reading what everyone is building and learning here.
Welcome to news members on DEV!
thank you!
Thank You Thomas.
Welcome to DEV! š
One of the things I love about this community is how it makes you feel that you're part of something. People take the time to read your work, encourage you, share their own experiences, help each other, and celebrate what you create. It's such a good feeling to see your work reach people and get appreciated, and to know that something you've shared might help someone else too. That's something I really value about DEV.
I'm so glad this community brings developers together like this, and I hope all the new members feel that same warmth here too. It's lovely to have you all with us. Wishing you all a great time being part of DEV! āŗļø
Hey everyone!
I'm Neha, a software engineer with 7+ years of experience, mainly working with React, TypeScript, and Node.js.
I enjoy working on complex web applications, especially frontend architecture, state management, debugging, and performance.
I've just joined DEV and published my first article, "Why Building a Reliable Calendar UI Is Harder Than It Looks." It shares a few lessons from working with scheduling interfaces, date handling, and frontend reliability.
If you're interested, here's the article:
dev.to/nehamangla/why-building-a-r...
Happy to hear how others approach similar challenges. Looking forward to connecting with the community!
Welcome Neha! A calendar post caught my eye: I build a content scheduler, and timezones plus "what day is this post actually on" have produced more bugs than anything else. Storing everything in UTC fixed the data but not the UI edge cases. Reading your article now.
Welcome all the new comers to DEV. š
It's a great community of developers, for the developers.
It's one of only a few places left where conflicting developer opinions rest in peace š¤£š„°
In case you are interested, here's one of my last posts that you may find worth reading:
There's No AI Agent, Nor Any Harness.
Hi all š We're Add to Calendar Lab. We compare add-to-calendar tools, the services behind those "Add to calendar" buttons on event pages and emails.
We came here to write about what we've learned building it: why calendar buttons break in Outlook, the .ics file rules nobody follows, and how we made the rankings checkable (the scoring code is public, so you can rerun it with your own weights).
Fun fact: Yahoo Calendar's add-event link ignores the
Zon a UTC time, so the same link shows a different hour depending on where you open it. There's no official documentation for any of these links, so we keep finding things like that.Glad to be here. If you've ever fought with time zones, say hi.
Hi everyone! I'm Ahmad, a senior software engineer with 14+ years building SaaS platforms end to end. These days I'm focused on AI agents, LLM retrieval and the systems that make them reliable. I just published my first post here, about why markdown plans break when you run multiple AI agents at once, and I'd love to hear how others coordinate their agents. Glad to be here!
Hi Ahmad and welcome ! A shared markdown plan broke the same way here: two workers could take the same unit. What held was a queue they pull from, with one session allowed to merge, and a dashboard so a stuck worker parks the question and takes the next unit instead of leaving the item marked in progress. I'd watch expiry on those claims: without it, a dead session still owns the unit.
Thanks Dominique! That's almost exactly where I ended up. Workers claim tasks from Postgres with a TTL, so a dead session loses the claim when it expires and someone else picks it up. I also added limits on refreshing a claim, because a stuck agent can keep refreshing forever without making progress.
Welcome Ahmad, and congrats on the first post! The markdown-plans problem sounds familiar. I run several coding agents in parallel on one repo, and what helped most was giving each one its own git worktree plus one shared lock for the heavy checks, so they stop stepping on each other's files and RAM. Shared plan files are still the messy part. Off to read your take.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.