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 (486)
Welcome everyone to dev.to! Glad you are here and hope you are well! I am a DEV Community Moderator and my primary goal is to support everyone on dev.to and ensure everyone is having a good time!
To get started,
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! 💡
Any questions about DEV and want to get answers from a DEV Community Mod? Leave a comment and come chat here!
Insights on Sloan and the MLH acquisition
Ask a DEV Community Mod! 🚀
Make sure to check out other resources here by other community members on dev.to: dev.to/help/community-resources
Feel free to introduce yourself and welcome others by replying to at least 2 people! It would be greatly appreciated! :D
Hope you are having a great summer and enjoy your stay here on DEV :D
Hey everyone, I'm Amy Lee. Just joined DEV and excited to be here. Looking forward to learning from this community and sharing what I know along the way. Feel free to say hi, would love to connect!
Hey! 👋 Nice to meet you. What are you currently working on?
Hey Amy!
hey
Hiii, nice to meet you💕
YEAH ME TOO
I'll love to connect too; just joined today
"Welcome! Same here, just started posting. What are you working on?"
HEEYYYYY
Welcome Amy
Welcome Amy! What brings you here on DEV specifically?
Hello everyone, I'm new here and very happy to join this developer community.
I mainly focus on backend development, frontend technologies, tool efficiency, and some engineering practices. I hope to learn from everyone's experience here and will try my best to share the problems I encounter, my solutions, and some insights during development.
If any questions are unclear, please feel free to remind me. I hope to communicate and improve together with everyone.
Nice to meet you all!
hi!
Hey Ami 👋!
Hi,Amy
Hi Amy! Welcome to DEV! What's your favorite programming language and why?
Hey Amy how are you doing? I'm new to the platform myself.
"Hey Amy, welcome! Just joined too, excited to be here."
hi amy im new too
Hello, Amy!
Hi
Hey Amy !!
Hi!
Hi Francis! Thanks for the warm welcome. I’m looking forward to learning and sharing battery-systems and engineering insights here. Do you have any tips for connecting with hardware or energy-storage developers on DEV?
Hey Mohammad and welcome to DEV!
I am not really familiar with hardware related stuff, but I do know there are some developers who worked with hardware (mostly arduinos). I only touch a bit on Arduinos stuff on dev.to when it comes to the ASL game. Though, it would be nice to see some more hardware developers on this platform, just as long as you are not sharing anything illegal lol
hey
Hey, I'm Alexis, I'm developing things in go!
Hey Alexis, happy to connect !
Greetings to all developers! 😊
Hi everyone!
I'm a MERN dev (MongoDB, Express, React, Node), currently learning advance backend engineering. Really excited to be part of this DEV community.
Looking forward to learning from you all, sharing what I'm building, and hopefully making some good connections along the way. Feel free to say hi !
Hi Isha, welcome
Hello all! Excited to join the community!
Hey Frank, happy to connect !
hii
Hello everyone 👋 , im new here... a little on my bg;
i build multi-agent systems, which mostly means watching very confident software fail in creative ways. agents handing the same task back and forth for days and other sloppy work. fun stuff... i know.
Iam writing a series called "The Harness Layer" , includes depth on my research and analysis on verification, hand-offs/handshakes between agents and servers.. and why evaluation from your model passes but the run still fails... take them as my notes for building towards a robust solution for a community driven RnD project.
anyway thats me boring you, what do you all work on, lets talk!🙌
Agents handing the same task back and forth for days - I fixed that with a counter, not a better prompt. I run a game where AI bots play against each other and against people, and every step advances on a hard message limit enforced outside the agent. Anything inside the agent gets argued with.
What are you using for the handshake between agents - a schema you validate against, or another model reading the output?
yeah makes sense. anything the agent can argue with, it will argue with. hard limit outside the loop is the boring fix that actually works. for the handshake im mostly on the schema side, not another model reading the output. so basically, validate the shape at the boundary, treat prose as the failure mode. a second model as judge just gives you a second opinion,
and yes ive watched that rubber-stamp a bad handoff more than once. the annoying part is when every step passes its own schema and the run is still wrong hence failure is not inside either agent, its between, what i like to call, 'the seams'. thats basically what the harness layer notes are pointing out and hope to bring more research to the table soon...
but curious about your AI bot game... how hardened is your message limit? is it fixed per turn, or does it scale with the game state?
Hey Azan! 👋 I'm new here too and just getting into open source. Your “watching very confident software fail in creative ways” line got me 😂
I'm working on AI-native developer tooling, so your work on multi-agent systems and verification really caught my attention. Keen to check out The Harness Layer!
Appreciate it Max. Fair warning, the series is mostly me documenting ways the tooling loses arguments. Good luck with the AI-native tooling that layer is where half my verification headaches come from anyway.😅
but looking to see if you have anything we interesting we can work on.
Hey Azan — finally read the latest Harness Layer piece properly. The line that stuck: "Generation was nearly free. Verification was the whole job." — and then the way the risk keeps moving, generation → verification → environment, each step less observable than the one before.
I think we're hitting the same problem from opposite ends. I've been writing about what interfaces should expose once agents, not humans, are the operators — one of my core lines is "expose the operational state, hide the implementation." That feels like your point from the other side: if the interface an agent drives doesn't surface its real state, a harness ends up verifying blind.
Which is concrete for you — Orcha plans/routes/verifies across MCP, A2A, and computer-use, so the super-agent is really an agent operating other software through a stack of protocols.
So: what should an interface expose so a harness (or a super-agent built on one) can verify what actually happened without fighting it? Feels like something concrete to build around — would love to compare notes.
Hi Azan, nice to meet you💕
Hello everyone, I’m Israel. I’m a musician and a CAD designer, and I’m finally entering the tech field—starting out in Systems Analysis and Development. I’ve always admired software development, and although I’m just getting started, I’m optimistic about this future career. I hope to learn and contribute to the community in some way.. 😎
Hey, Israel! Nice to see a fellow musician :). What do you play?
Show, Clarinet and Sax
Oh, hey Israel santos ,are you new here?
Hi Israel! I’m also just starting my journey in tech and studying Computer Science. It’s nice to find other people beginning this path too. Wishing you a great journey!
Hi everyone! 👋
I'm Charlie from Taiwan. I'm currently an undergraduate student working on mathematics, AI, and open-source developer tools.
I enjoy building things around research tooling, CI reliability, and AI-assisted development. I'm currently experimenting with a project called HonestCI, which started from a simple question: does a green CI check really mean the tests we expected actually ran?
I'm looking forward to learning from the DEV community, sharing what I discover, and getting feedback from people building real-world software. Nice to meet you all!
Taiwan No1！
🥰
Hi everyone!
I'm Luiz, from Brazil. I'm switching careers into tech after a background in Biotechnology and a Master's in Chemical Biology, where I spent years analyzing experimental data and documenting complex processes with a lot of rigor.
I'm currently studying Systems Analysis and Development, learning Python, APIs, and databases, and I'm genuinely excited about applying AI tools to real development workflows (I've been using Claude Code to automate parts of my own job search, actually).
Looking forward to learning from this community and sharing what I build along the way. Happy to connect with anyone else who's also transitioning into dev from a different field!
Hi Luiz! Nice to see another Brazilian here. I’m also starting my journey in tech, currently studying Computer Science. Your career transition is really interesting. Looking forward to following your progress!
Hey Luiz — I came into dev from marketing, so I know that jump well. The
"documenting things with rigor" habit helps way more than people expect.
Curious what you automated in the job search with Claude Code?
Thanks Oleksandr! Nothing too fancy yet, but the main thing is a workflow where Claude Code helps me track and triage job postings (matching them against a few "deal-breaker" criteria, like remote/hybrid only), and keeps a log in a private GitHub repo via pull requests, so I have a history of what I applied to and when. Still evolving it, but it's saved me a good amount of manual tracking. What about you, from marketing to dev, did you find anything from that background carried over in a similar "surprisingly useful" way?
That's interesting career graph, Luiz. Happy to connect !
Hi everyone! 👋
We're ArtClick, a web development studio based in Kyoto, Japan. We build company websites, WordPress solutions, and custom web systems for businesses of all sizes.
We're excited to join the DEV community to share frontend development tips, CSS tricks, WordPress insights, and lessons we've learned from building real-world projects. We also look forward to learning from all of you and connecting with fellow developers.
Looking forward to being part of the community! 🚀
Hey everyone! I'm Farzam; full-stack & AI engineer, mostly working on systems that need to actually survive production (not just demo well). Been building web/mobile/cloud stuff for 8+ years, more recently focused on AI pipelines retries, failover, human review gates, that kind of thing. Looking forward to sharing what I learn here 👋
Retries are the part everyone gets wrong first. Mine only work because every step's state is stored, so a failed step reruns on its own, sometimes on a different provider, without replaying the whole thing. Failover sits above the agent, not inside it.
Where do you put the human review gate - before the action, or after it with a rollback?
Before, in this case. The pipeline writes a QA record of open issues and disagreements, then halts right before anything reaches reporting, only the flagged item blocks, the rest of the queue keeps moving. Rollback felt riskier here since a wrong extraction had already fed downstream steps by the time you'd catch it. Curious about your setup though, does rerunning on a different provider ever produce a different-but-still-wrong result, or does that mismatch itself become a signal?
Hello everyone 👋🏼
I'm Behzad, a Software Engineer working mostly on backend systems with Go, and occasionally PHP and Python when I have to, but Go is where my heart is. Over the years I've also led engineering teams, from small startups to larger product teams.
I'm a bit obsessive about code quality. clean, readable, maintainable, and extendable code isn't optional for me. That's also why, in the age of AI assisted development, I review every line of AI generated code very thoroughly before it goes anywhere.
What brought me here? I've been reading dev.to posts for a long time, but always as a silent reader and never dared to post anything. I finally decided it's time to be on the other side and sharing my own experiences and thoughts with the community.
Hi everyone! I'm a solo/beginner app dev. I learn to build small, useful mobile apps one at a time. I just released my first app, Dormeil, a bedtime-routine coaching app. I'm new to building in public and I'm here to learn from this community, share what I run into along the way (localization, marketing on near-zero budget…), and hopefully make some good connections. Feel free to say hi !
Hey everyone! 👋
I'm a Data Scientist and Software Developer focused on AI, machine learning, RAG, LLMs, and ML systems.
I'm particularly interested in how we build, evaluate, and scale AI systems in practice.
I'm starting RAG Under the Microscope a series where I dig into RAG systems(3 architectures), test the assumptions behind them, and see what actually holds up when you look closely.
I'm joining DEV to learn from the community, share some of the projects I'm working on, and connect with other people working in AI and software engineering.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.