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 (511)
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, I recommend reading this guide on making the most out of dev.to!
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! 💡
Make sure to check out other resources here: dev.to/help/community-resources
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! 🚀
Feel free to introduce yourself and welcome others by replying to at least 2 people! It would be greatly appreciated! :D
im harish, from a small village in india
welcome, harish
hello
welcome Harish
Hello Harish, nice to meet you, I am Andrei and like you joined the dev.to Community just now 🎉
Hey Andrei. welcome to the dev.to community
Welcome, Harish! Great to have you here. What are you working on or hoping to learn? Plenty of friendly people around to point you at good resources.
Welcome Harish!
nice to meet you
hola, yo soy de el salvador
Hi I'm Matt, a freelance web designer and developer from Cambridge, UK.
I'm pretty new to the industry, self-taught over the last couple of years. I've mostly been working in WordPress with a custom starter theme (gulp, scss, php, gsap) that I learned from an agency.
More recently, I've been experimenting with JAMstack and just rebuilt my portfolio site with it.
I'm really keen to keep learning more, get more exposure to real-life projects, and offer my support to small agencies who might need some extra help.
nice meeting you
Thanks Francis! Happy to be here — this looks like a great community to learn in 🙌
I’m Kael, from Singapore.
I mostly build tools for stock research and backtesting. Lately I’ve been working on
volas, a super-fast, Rust-backed, pandas-like DataFrame for OHLCV data, which has 254 built-in technical indicators. 😃I’m here to learn from people working with Python, Rust, data engineering, and market data tools. Nice to meet everyone.
hello,Kael.Welcome to dev.
Hey Kael, welcome to dev.to community
Hello Kael, Nice to meet you.
Hi all, I'm Scott from central Wisconsin, USA, and I just joined today. As you'll see if you look at my profile, I build WordPress websites for a living. Any of you who build websites, WordPress or not, knows that creating a good website requires many, many skills. So I thought, what better place to learn about a wide variety of topics, and that's how I ended up on dev.to.
Hi Scott, nice to meet you.
I've mostly been working in WordPress too. What tools do you use to build your WordPress websites?
Most recently, I've been using Claude Design to generate HTML which I then insert into HTML blocks in the Gutenberg editor, interspersed with GenerateBlocks in a GeneratePress theme. It works surprisingly well once you figure out a scheme to prevent CSS from Claude from stomping all over the GP/GB CSS.
Hey everyone! Senior sysadmin here. Just deployed my lightweight open-source behavioral network-socket monitor to GitHub. Excited to join the community and looking forward to sharing ideas and reviewing codebase architectures with you all!
Welcome! A lightweight behavioral socket monitor is a great niche to own, the kind of thing you end up reaching for constantly once it exists. What pushed you to build it from scratch rather than wire up existing tooling? Always good to see more people shipping open source here.
cool, how's going? I am starting with open source project as well, good to see more open source devs here.
Coolll
Amazing!
Hey everyone! I'm Amer, an IT and Network Infrastructure expert. I've been in the tech field since 1998, focusing on network maintenance, hardware, and recently, cybersecurity. I'm excited to join the DEV community, connect with fellow developers, and share insights from my long journey in tech. Looking forward to learning from you all! 🙂
Welcome @icoreux ! Dev is a great and welcoming community. Looking forward to reading about your journey!
welcome to dev.to
Hey everyone! I'm Jay, 24 years old from Munich, Germany.
I'm building APIs on the side — currently running a validation toolkit on RapidAPI (IBAN, email, phone, VAT, password breach-check and more). Also into trading and building my own AI dashboard.
Always happy to connect with other builders and developers. Looking forward to the community!
Hey Jonas. Welcome to the community. 😊
Wow, an API builder. Truly honored to meet you. What's your favorite API that you have build or used that have blown you away.
Awesome to have you here and have a great time here.😉
Thanks for the warm welcome! 😊
Honestly, the one that blew me away to build was the password breach-check endpoint — it uses HaveIBeenPwned's k-anonymity protocol, so only a 5-character SHA-1 hash prefix ever leaves your server. The full password never gets sent anywhere. Simple concept, but elegant privacy-by-design.
Currently working on a full validation toolkit (IBAN, VAT, email, phone, disposable email detection and more) — happy to share if you're curious!
Looking forward to connecting with everyone here 🙌
Wow, completely blown away by your sharings. You explained it like I'm 5. Sure, I would love to know more about it and all the best for it. Hope it comes and becomes Product of the Day on Github.
Hello Jonas :D
Hi 👋
Evgenii, from Valencia, Spain. I run a small web studio — React, TypeScript, Django, and lately a lot of LLM agents.
What brought me here: I keep finding the same problem on different clients' sites, and it isn't really a bug. People assume that if Googlebot can render their site, AI crawlers can too. They can't. I started writing about it, and this looked like the place where someone would actually argue with me. Please do.
Fun fact: I spent 12 years servicing medical lab analyzers before I touched the web. 300+ labs, coagulometers, immunoassay machines. Turns out debugging a React hydration issue and debugging a machine that hands someone the wrong blood test result use the same part of your brain. One of them just matters more.
Currently learning: what AI crawlers actually do — by reading server logs instead of vendor blog posts. Recommend it.
You asked for an argument, so: how long does the problem even last? Crawlers that can't render JS feels like a today-problem - the newer agent browsers drive real Chrome and render everything. My money is still on server-rendered HTML winning, just for a different reason: it's cheaper for the site than letting a thousand agents each run your JS. And 12 years of servicing lab analyzers is the best origin story in this thread.
Fair, and partly right. The agent browsers (ChatGPT agent, Perplexity's) do drive real Chrome and render everything. For those, JS is a non-issue.
But that's a narrow slice. The heavy lifting is GPTBot, ClaudeBot, Meta-ExternalAgent, and as of June 2026 none of the major AI crawlers render JS (Lantern's monitoring, plus a pile of May audits saying the same). The one exception is Gemini, and only because it rides Googlebot's infra. Meanwhile the volume is growing, not shrinking: GPTBot is up ~305% year over year per Cloudflare. So it's not a fading problem, it's scaling.
Which flips your framing, not mine: rendering at index scale is too expensive for them, so they don't, so the HTML has to carry the content. The day GPTBot renders JS at crawl scale I'll happily retract the post.
Your cost angle is the stronger version, honestly. "Cheaper for the site" beats "required for visibility" because it holds even in a fully-rendered world. Stealing that.
(And thanks re: the analyzers. Still not sure if it's a flex or a warning label.)
Deal - you take the cost angle, I'll take the correction. I was arguing from the session end (agent browsers); at crawl scale your numbers win. And 305% more crawling with zero rendering means they're scaling the cheap path, not working toward the expensive one. It's a flex, by the way.
"Scaling the cheap path, not working toward the expensive one" is the line I should've led with. 305% growth with zero rendering isn't a company that hasn't gotten to JS yet — it's a deliberate architecture. You don't scale something 3x while planning to replace it. Good arguing with you.
(Noted. Filing it under flex.)
👋 Hi everyone! Excited to be here!
I'm a developer interested in AI, Computer Vision, and Automation. I enjoy building practical AI applications and sharing what I learn along the way. Most of my current work revolves around Oglas AI, where I'm focused on applying AI to real business use cases.
Looking forward to learning from the community and contributing through articles and discussions. 🚀
Hey Oglas! Welcome to DEV! Looking forward to read your first article!
Same here - Would like to read your post
Welcome! Best of luck, mate!!
helloo
hi
Hi everyone! I’m a software engineer focused on production AI applications, Java backend systems, and business process automation.
I enjoy building practical tools that connect modern AI capabilities with existing business systems and operational workflows. I’m also exploring Microsoft Dynamics 365, Power Platform, and new approaches to modernizing business applications.
I joined DEV to share what I’m building, write honestly about engineering with AI tools, and learn from other developers working on real-world systems.
Hey Richard. Welcome to the community. 😊
What's your daily AI tool or an AI workflow that you have created for yourself? Looking forward for your articles and learning from them.
Have a fantastic time exploring!
Thanks for the warm welcome! 😊
My daily AI tools are mainly ChatGPT and coding assistants such as Codex or Cursor. I use them for exploring architecture decisions, reviewing code, debugging, and turning rough technical ideas into clearer implementation plans.
One workflow I’ve developed is using AI as a structured engineering partner: first defining requirements and constraints, then generating a plan, implementing in small steps, and reviewing the result rather than accepting generated code immediately.
I’m also interested in writing about how AI tools improve developer productivity—and whether relying on them too much can affect how we build our own engineering judgment.
Hello Everyone, I am Georgii, software dev, working mostly with high throughput analytics. Recently started building AI agentic systems and now I am building my own project AgentArmory - Skills via MCP, always tuned, always fresh.
Skills that stay tuned is the hard half - mine go stale the moment the environment shifts under them. I ended up letting a model maintain them, with hooks that force a compaction when a skill overgrows. Curious how AgentArmory decides a skill needs a refresh.
Hi Aliaksei, thank you for the question. Regarding overgrowing, the skill tuning is never just append, it should be dense enough, so instead a fresh look is taken before the edit.
Regarding how to maintain the skills, mcp features feedback tools and harness can report staleness, and is actually encouraged by tool descriptions.
Hi all! Joining the community as a Systems Engineer & Security Researcher. I focus on low-level tooling and hardened infrastructure. Currently hacking on PtyXL project. If you're into Rust, Tauri, CyberSecurity, or dev-tools, I’d love to connect and talk!
Hi. Welcome to the Community 😊.
Can you explain PtyXL project or is it Top Secret Mission that will be discussed later?😆
Awesome to see you! Enjoy the vibe. 🫡
Haha, absolutely - no corporate secrecy here, just a strict local-first philosophy. 😆
PtyXL is a modern local-first terminal client for SSH, SFTP, and Serial, written entirely in Rust with Tauri. Zero cloud sync, zero telemetry, and full data sovereignty for your infrastructure credentials.
We also just shipped the Provision Builder in v0.5.8, letting you orchestrate server configurations and pipelines by connecting logic tiles instead of writing raw shell scripts.
Appreciate the warm welcome! 🚀
This sounds too awesome. I would to try it and learn from you. Thank you so much for creating it. I wanna get my hands dirty in CLI or API building haha. Someday, I'll post about my projects too.
Awesome to have you. Keep building and breaking.😁
Thanks, that means a lot! Would love to have you try it out. If you hit any rough edges or have ideas, I'm all ears, still very early and shaping the roadmap based on exactly this kind of feedback. And yeah, definitely post about your projects - always good to see what people are building. 😄
Hi everyone,
I'm excited to join the DEV Community!
I've created two posts on dev.io to share, and am looking forward to discussing them with you all. I have 25+ years of experience in software engineering, AI/ML, data analytics, and technical leadership. Recently, I've been exploring how Large Language Models (LLMs) can help solve real-world software engineering challenges, such as Jira backlog analysis, project management, and developer productivity.
I'm currently writing about practical AI applications, prompt engineering, RAG, and LLM evaluation, and I look forward to sharing what I learn while learning from this amazing community. Comments and feedback are always welcome.
Outside of coding, I enjoy mentoring, continuous learning, and building projects that bridge AI research with practical engineering. Looking forward to connecting with fellow developers. Thanks for having me!
Hey K Gann. Welcome to the community. 😊
Which is the best AI software that you feel caught your attention and you enjoyed using it. Like WisperFlow or any other. What are the key lesson that you have learned about AI.
Awesome to have you here and have a great time here.😉
Thanks for the warm welcome! 😊 I haven't tried WhisperFlow yet, but I've been using Colab with Gemini Flash for coding, Perplexity for research (love that it cites sources), and rotating between ChatGPT, Claude, and Gemini depending on the task. Biggest lesson so far: each model has its own strengths, so it's worth trying a few rather than sticking to just one. Excited to be here and learn from everyone!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.