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.
Re...
For further actions, you may consider blocking this person and/or reporting abuse
Hi! I am Ripa. Now I am learning CSS. Almost finished, just trying to strengthen my site in responsive design. I heard about this from Programming Hero. So here I am.
Hey Ripa! Great to have you!!
welcome Ripa!
Welcome welcome welcome everyone! Please don't fee shy to comment here or anywhere else on the site with questions, suggestions, whatever.
Hi Dev.to 👋
I'm a Go / Vue dev based in Ukraine, and for the past year I've been building something called Road511 — a REST API that normalizes real-time traffic data from every US state and Canadian province 511 system into one
consistent schema.
Over the next 6–8 weeks I'll publish a deep-dive series about the technical decisions behind it. If you work on data pipelines, API design, geospatial systems, or you've ever tried to integrate 30+ upstream services with 30+
different schemas — this one's for you.
## Why Road511 exists
Every US state and Canadian province runs its own "511" traveler information system — traffic events, road conditions, cameras, DMS signs, rest areas. They all serve the same kinds of data. They all do it differently:
Want cameras for a cross-state trip? That's five integrations, five auth flows, five update schedules.
Road511 aggregates 80+ source servers into one REST API with a unified schema. One call, one key, one response format.
## What's in the data
Every endpoint has a GeoJSON variant. Drop it into Leaflet or Mapbox and it just works.
## The series
Already published:
Coming up — expect one post per week:
Follow the series tag (sidebar, right) if you want new posts to land in your feed automatically.
## Stack
cmd/api(public API + customer portal) andcmd/worker(scheduler + adapters + admin)## Try it
If there's a 511 system I haven't covered, a feature you wish existed, or a data source I should look at — drop it in the comments. I'm actively building and this series will shift based on what people actually want.
See you in the next post.
Hi, I'm Bobby. I'm a full-stack web developer, and over the next year, I'm going to work on a series of side projects I've been meaning to tackle. It's going to be a series of blogs recording my progress. Feel free to ask me anything!
Hey everyone! 👋
I'm building Hermetic — an Agent-Isolated credential broker for AI coding agents, written in Rust.
The problem: if you use Claude Code, Cursor, or any MCP-compatible IDE, your API keys sit in plaintext config files. If the agent gets compromised, every credential is exposed.
Hermetic fixes this: the daemon makes the API call on the agent's behalf and returns only the response. The agent never sees the credential. Domain binding ensures a Stripe key can only be sent to api.stripe.com — the agent can't override it.
Just published my first blog post here — an analysis of GitHub's new AI agent security game (Secure Code Game Season 4) where I mapped every level's vulnerability against credential isolation:
dev.to/hermetic3243/i-played-githu...
Currently: zero users, lots of tests (1,040+, 1.7B fuzz executions), and figuring out how to get people to actually try it. Happy to connect with anyone working on AI agent security or Rust tooling.
GitHub: github.com/hermetic-sys/Hermetic
Hola! I am Stacey, cofounder of an AI company, PromptOwl (promptowl.ai) and the open source project Context Nest (github.com/PromptOwl/ContextNest).
We founded PromptOwl to study and build the things that enterprises will need to run grown-up AI — context management, governance, security, and making real agents with tools and context and auditing from regular language. And all the plumbing to make it not fall over or hallucinate.
I have been in the AI/ML arena for nearly 15 years, and know instantly that AI is currently built for individual use, and even then it isn't optimized. The enterprise has a real gap to cover before they can embrace AI unfettered.
The interesting problem isn't the model anymore. It's everything around it—the context architecture that lets your AI know what it's allowed to see, the governance that keeps it from hallucinating, the security that makes auditing possible, the development practices that work when you're building systems that are part AI and part traditional code.
I'll be writing about that here on Dev.to—the infrastructure layer that separates prototype from production.
Hi DEV Community!
I’m Hema — a SDET with 9 years of experience in software testing and quality engineering. I’ve recently started learning machine learning, generative AI, and responsible AI from a QA perspective, and I’m documenting my journey learning in public.
I regularly share my learnings and AI‑focused QA insights on my blog as well:
hemaai.hashnode.dev/
Excited to be part of the DEV community and to learn, share, and grow together. Feedback and conversations are always welcome! 😊
Hi everyone,
New to the scene and loving it here. Hope to learn as much as I could in here.
Hi folks!, sharing finding I find day-to-day in engineering. I love to hike!
Hello, Entflow here! Ready to rock & roll your Hubspot portals 🫡
Hi, I am Sri balagi. I am AI&DS undergraduate and am delighted to get into this community. Interested in finding out what i can learn from here.
hi. i am kk now i know c,c++ and python and i am 11
Hi, dev.to!
Building something and may find some answers here :)
I am Maneesh from India,
HEY! Just a guy from Venezuela, living in Medellín, no fancy education, teaching myself AI through trial and error. ADHD keeps me grinding; coffee keeps me going.
Hello!
Hello everyone!
Hi everyone 👋
I’m Aayush Kumar, a software developer passionate about building and learning new things.