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
Displaying a subset of the total comments. Please sign in to view all comments on this post.
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 Francis, your font formatting is off the charts. Fun!
Hello together,
I'm a platform engineer and currently learning go and C# to develope some stuff by myself.
Here at dev.to, I want to write articles about tools which I use daily at my work as well as my journey learning programming languages and building my dreamed use-cases (without AI assistance, hardcore mode).
This is pure training to document stuff and hopefully I can help someone with my documentations and links to my github repo's.
Thank you for having this post here :)
That's inspiring! Looking forward to your GitHub projects!
Hi everyone! 👋
I'm a developer with a background in Mathematics and Computer Science. I work across web development and design, and I build small data and scraping tools as well.
Lately I've been focused on Apify. I create small, focused tools there that pull hiring signals, detect a website's tech stack, and track public data sources like vehicle recalls and nonprofit filings. I try to keep things simple. Most of my tools use passive lookups instead of proxies or headless browsers.
I found DEV Community while looking for other builders working on similar problems, and I wanted to join in and start sharing what I learn.
My goal is to keep building useful tools, write about the process, and learn from everyone here.
Looking forward to connecting with you all! 🚀
Passive lookups over headless browsers is the default I would pick too. It works until the thing you need is only rendered behind a login.
I track spend across eleven AI providers. Five expose it through an API. The other six I read with a headless Chrome session over CDP, because the balance is drawn in a dashboard and nowhere else. It is the most fragile thing I run and there is no passive version of it.
For hiring signals and tech stacks, has passive been enough, or is there a category you gave up on?
That CDP setup for the 6 dashboard-only providers sounds like exactly the kind of thing I'd want to avoid building if I could. Respect for keeping it isolated to just the providers that actually need it.
To answer directly: for tech-stack detection, passive has been fully enough. Everything I check is already sitting in the first HTTP response, headers and static HTML markers, so there's nothing hidden behind auth or client-side rendering to chase.
For hiring signals it's more of a coverage limit than a technical one. Greenhouse and Lever both expose their job boards as public JSON APIs, so any company on those two is fully passive. But that's only two ATS platforms. Workday, iCIMS, a custom in-house careers page, none of those expose anything passively, so those companies just aren't covered right now. I haven't tried to fix that with a browser layer since it would only reach a handful of new companies at a real maintenance cost. Curious if that tradeoff matches what you've seen elsewhere.
Ⓦⓔⓛⓒⓞⓜⓔ ⓣⓞ ⒹⒺⓥ! 🌸✨
𝓨𝓸𝓾𝓻 𝓫𝓪𝓬𝓴𝓰𝓻𝓸𝓾𝓷𝓭 𝓲𝓷 ᴹᵃᵗʰ ᵃⁿᵈ ᶜᵒᵐᵖᵘᵗᵉʳ ˢᶜⁱᵉⁿᶜᵉ ꜱᴏ ᴄᴏᴏʟ! 📐💻 𝕀𝕥'𝕤 𝕤𝕠 𝕣𝕖𝕗𝕣𝕖𝕤𝕙𝕚𝕟𝕘 𝕥𝕠 𝕤𝕖𝕖 𝕤𝕠𝕞𝕖𝕠𝕟𝕖 𝕗𝕠𝕔𝕦𝕤𝕚𝕟𝕘 𝕠𝕟 𝕝𝕚𝕘𝕙𝕥𝕨𝕖𝕚𝕘𝕙𝕥, 𝕖𝕗𝕗𝕚𝕔𝕚𝕖𝕟𝕥 𝕤𝚌𝚛𝚊𝚙𝚒𝚗𝚐 𝕥𝕠𝕠𝕝𝕤 𝕝𝕚𝕜𝕖 𝕥𝕙𝕠𝕤𝕖 𝕠𝕟 Apify. 🚀✨
ⒷⒾⒼ 𝓚𝓤ⓉⓈ (Cheers) to keeping things simple! Looking forward to following your journey and reading your articles here. Have a wonderful summer! ☀️🌻
Thanks for the warm welcome😃
Passive lookups over proxies/headless browsers is a smart default — way less to maintain, and way less likely to break silently when a site changes its layout.
Curious about the tech-stack detection one specifically — are you doing that mostly through response headers/meta tags, or going deeper (JS framework fingerprinting, that kind of thing)? I ask because we occasionally need to quickly gauge what a prospective client's current site is built on before quoting a migration, and I've always just eyeballed it manually.
Also respect the "keep things simple" philosophy — most tool-builders overcomplicate the scraping layer way before they need to.
Hey everyone 👋
I'm Cédric, co-founder at Kardinal. Spent most of the last ten years buried in the modeling side of vehicle routing, the part where a business rule has to somehow become something a solver can actually work with. Lately I've been digging into whether an AI agent can pick up that same skill, reasoning about which constraints apply instead of just calling an endpoint and hoping for the best.
New here, and this place already looks like a goldmine, especially on the AI and agents side, which is pretty much what I spend my days on right now.
Curious what people are running into with agents and real-world tool use lately. What's been the hardest part for you?
Looking forward to learning and connecting with everyone here 😊
Ⓦⓔⓛⓒⓞⓜⓔ ⓣⓞ ⒹⒺⓥ, Ⓒéⓓⓡⓘⓒ! 🌸✨
𝓣𝓱𝓪𝓽 𝓲𝓼 𝓼𝓾𝓬𝓱 𝓪 𝓬𝓸𝓸𝓵 𝓷𝓲𝓬𝓱𝓮! 🚚💨 Vehicle routing and constraint modeling are heavy-duty problem spaces, so bringing agents into that mix sounds like an epic challenge.
🅃🄷🄴 🄷🄰🅁🄳🄴🅂🅃 🅟🄰🅁🅃 ⓕⓞⓡ 𝓂ℯ with real-world tool use has been keeping agents from hallucinating parameters when tools require strict, highly specific data schemas. 📉🧩
𝕊𝕠 𝕘𝕝𝕒𝕕 𝕪𝕠𝕦 𝕗𝕠𝕦𝕟𝕕 𝕪𝕠𝕦𝕣 𝕨𝕒𝕪 𝕙𝕖𝕣𝕖—𝕕𝕖𝕗𝕚𝕟𝕚𝕥𝕖𝕝𝕪 𝕒 𝕘𝕠𝕝𝕕𝕞𝕚𝕟𝕖 𝕗𝕠𝕣 𝔸𝕀 𝕥𝕒𝕝𝕜𝕤! 🚀 𝐻𝒶𝓿ℯ 𝒶 𝓌ℴ𝓃𝒹ℯ𝓇𝒻𝓊𝓁 𝓈𝓊𝓂𝓂ℯ𝓇! ☀️🌻
Hi Cedric, welcome. On agents and real tool use, from the other side of the wire: I run the API and MCP server that agents call, and what breaks most is that an agent acts on what an error says, not on what it means.
Last week my own rate limiter answered a burst with Retry-After: 2. The header assumed the overage drains at the speed of the sliding window, but the requests causing it sat in the current minute and didn't move until the minute rolled, so the true wait was about 30 seconds. Every well-behaved client slept 2 seconds, got the same answer, and quit. The rude ones that ignored the header and hammered got through.
So what's been difficult isn't the agent reasoning about which constraint applies. It's that a tool has to be honest in its failure modes, because an agent takes a wrong number at face value in a way a person never would.
U.S. Business Partnership Opportunity
We’re a Japan-based software development team looking to build a long-term partnership with a reliable U.S.-based professional.
Our team handles the technical side—from development and testing to project delivery. We’re looking for a U.S. partner who can help with client communication, business coordination, and developing new opportunities in the U.S. market.
This is a revenue-sharing partnership, not a traditional employment position. Partners can receive 30–35% of the agreed revenue/profit share, depending on the project and responsibilities.
If you’re interested in technology, freelancing, or building a side business and would like to learn more, send me a DM. I can provide the details, expectations, and example project structure.
I built an email agent for my home lab, and it fetched messages with the wrong IMAP command. That command sets the "seen" flag as a side effect, so it quietly marked 9,133 of my 9,143 personal emails as read. I wrote that one up, because the write-up I wanted to find while I was debugging it did not exist.
That is mostly what I do here. I run a home lab like a small company — a Proxmox cluster of about twenty containers, self-hosted single sign-on, a mesh VPN, a secrets manager, Home Assistant, and a set of LLM agents that share a task board and have separate jobs. I write up what broke and what the real numbers were, rather than the tidy version. Five trading bots that reported every sale as a success and had never sold anything was another one.
I only started publishing on 5 September, so I am still finding my feet. If you write up your own failures rather than your wins, I would like to read them — who should I be following?
Home Assistant is a cool project. I gave up on mine because it's too much work and it's too self-focused - it's hard to share it with other people. That's why I prefer to build games with AI.
I also have loop-agents for multiple automations I need, and they are not that reliable. Every week something breaks in them despite all the self-checks and their ability to fix their own bugs. So Home Assistant is a bit scary. Even Google cannot make one properly. I have some Google devices in Google's assistant ecosystem, and it's not that great.
Hey DEV, I'm a full-stack engineer working across React, Next.js, NestJS, and PostgreSQL. Recently, I've started writing up the engineering problems I actually hit in production.
My first piece here is about a theme toggle that crashed the app in production: a hydration mismatch that turned into a blank screen under a Trusted Types policy, and why the usual
mounted-flag fix wasn't the right fix. Fixing the issue forced me to understand React's hydration recovery a lot more precisely than I expected.I'm here to write from real incidents, and to learn from how the rest of you approach this stuff. Glad to be a part of the DEV community.
The Trusted Types + hydration combo sounds genuinely painful to debug — that's the kind of bug where the error message and the actual root cause live in completely different parts of the stack, so I imagine the mounted-flag instinct made sense at first before you dug deeper.
Curious what actually pointed you toward the real fix — was it something in the CSP violation reports, or did you have to trace through React's hydration internals directly to figure out why the usual workaround wasn't sufficient here?
"Writing from real incidents" is a good approach — most React content out there is tutorial-shaped, not incident-shaped, so there's a real gap for the "here's what actually broke and why the obvious fix didn't work" kind of writing.
Good question, and you pinned the exact pain: the throw and the root cause were nowhere near each other.
What pointed me at it was the enforced Trusted Types policy. When the hydration mismatch happened, React's recovery path tried to write the corrected markup through innerHTML, and the policy only defined createScriptURL (for the chunk loader), not createHTML. The throw is what dragged my attention to the recovery path specifically, which is not where you'd instinctively look for a "theme flash" bug. I confirmed the hydration behaviour against React's source.
I did reach for the mounted-flag "fix" first, and it does stop the crash, because server and client agree on the first render. But it bugged me that the mismatch still existed: hidden, not removed. Once I arrived at "the real theme already lives in the DOM before React runs, React just needs to read from the real source of truth", useSyncExternalStore came up naturally: on the first render both server and client return the same fixed value, so they agree by construction, then it reads the real value from the DOM afterward. No mismatch to recover from, no innerHTML write to reject.
And yeah, memory is unreliable, which is half the reason I keep a decisions.md. This one had a written record of the incident, so the writeup is the real chain, not a reconstruction.
Appreciate the "incident-shaped vs tutorial-shaped" framing, that's exactly the gap I'm writing into.
hi every.Here is VoltWake and I'm an indie builder.
I'm currently focused on building with AI coding agents like Claude Code and Codex, and figuring out what they're actually good at (and where they still fall short).
I'm here to learn from the community, share what I'm building, and connect with other developers. 🚀
Looking forward to learning and connecting with everyone here!
Hey Chaos! 👋 Welcome to DEV!
VoltWake sounds like an exciting project! Love that you're exploring AI coding agents and figuring out what they can actually do. Excited to see what you're building and learn from your experiments. Looking forward to your posts! 🚀
hey Chaos 👋 what kind of tasks have you been testing Claude Code and Codex on? i'm building Empryo, so i'm interested in the same question from the harness side.
codebase awareness and token usage were what pushed me to build it. curious whether your harder failures happen while finding the right code or after the agent has already found it. do you keep a repo instructions file, or end up explaining things again each session?
Welcome VoltWake! 👋
Super interesting that you're exploring AI coding agents, I'm curious about the same space from the reliability side. I've been building RAG pipelines and LLM systems, and the biggest lesson has been that these models are great at reasoning but still need a solid system around them to be trustworthy.
Would love to hear what you find about where Claude Code and Codex fall short, that's honestly the more interesting part. The failures teach you more than the wins!
Let's connect!
Hello everyone 👋
My name is Carl Lindberg and I am a Microsoft Azure MVP with a special interest and focus on infrastructure as code (IaC).
My language of choice when it comes to IaC is Terraform, but I have used Azure Bicep as well before. I come from a traditional IT background. Today I work as a cloud engineer, and I make videos on my YouTube channel and I post blog posts about Azure Cloud, Terraform, agentic AI, and much, much more. I have already published one post on here, which is called "Terraform State Explained," which you can find on my profile. I wasn't sure if I was allowed to share it in a comment here. Really glad to be here, and hope you're all doing well. 😊
Hey Carl! 👋 Welcome to DEV!
Your work with Azure, Terraform, and Infrastructure as Code sounds really exciting! Excited to learn from your experience and explore your posts on cloud and agentic AI. Looking forward to connecting and learning from your journey! 🚀
Hi Carl, welcome to dev.to!🥳
Nice to see an MVP here for stuff I do daily in Azure.
U.S. Business Partnership Opportunity
We’re a Japan-based software development team looking to build a long-term partnership with a reliable U.S.-based professional.
Our team handles the technical side—from development and testing to project delivery. We’re looking for a U.S. partner who can help with client communication, business coordination, and developing new opportunities in the U.S. market.
This is a revenue-sharing partnership, not a traditional employment position. Partners can receive 30–35% of the agreed revenue/profit share, depending on the project and responsibilities.
If you’re interested in technology, freelancing, or building a side business and would like to learn more, send me a DM. I can provide the details, expectations, and example project structure.
Hey everyone! I’m Michael.
I’m an open-source developer currently building Network Doctor, a cross-platform terminal tool written in Go for diagnosing network problems like DNS, TCP, TLS, proxies, routing, and more.
Lately I’ve been spending a lot of time improving the project, learning more about networking, and figuring out how to make developer tools easier to understand instead of just dumping a wall of technical information on people.
I joined DEV to share what I’m building, learn from other developers, and meet more people working on open-source and terminal tools.
Nice to meet everyone! 👋
Hey Michael! 👋 Welcome to DEV!
Network Doctor sounds like a really interesting project! Love the idea of making networking tools easier for developers to understand. Excited to see what you're building and learn from your open-source journey. All the best! 🚀
Thanks so much! I really appreciate the welcome. I’m hoping Network Doctor can make troubleshooting less intimidating and a bit more understandable for developers. Glad to be here! 🙌
Hey Everyone,
Jared here, I have lots of scare tissue and calluses from building & breaking software over the last 17+ years. I'm here to hopefully learn, read content not entirely generated by LLMs and write about some things I'm busy with. I love JS, TypeScript, Rust, PHP, beautiful UIs and performant systems.
Much love to you all ❤️
Hey Jared! 👋 Welcome to DEV!
17+ years of building and breaking software is an amazing journey! Your love for beautiful UIs and performance systems sounds really interesting. Excited to learn from your experiences and see what you share with the community. Much love! ❤️
Hi everyone. I'm Mark, I run a small penetration testing firm in New York. I came here because most of what our team learns comes from other people's write-ups, and it felt like time to give some back: we'll be posting about web, API and cloud testing, and about what the compliance frameworks actually ask for versus what people think they ask for. Currently learning more Nim than I expected to, because one of our internal tools ended up written in it. Fun fact: the best finding I ever saw came from a tester who read the documentation instead of running the scanner.
Hey Mark! 👋 Welcome to DEV!
Your approach to penetration testing sounds really interesting. Excited to learn from your write-ups on web, API, and cloud security. That documentation vs. scanner story is a great reminder that sometimes the simplest things make the biggest difference. Looking forward to your posts! 🚀
Hey everyone! 👋
I'm Piotr, a software engineer with a background in building full-stack web applications, low-latency and applied AI infrastructure.
I've been reading articles on DEV for a while, and I decided it's finally time to stop lurking and start sharing real-world engineering notes from production.
What I care about:
What I'm currently working on:
wavy-soundson npm).I'm here to exchange ideas, get challenged on architectural decisions, and learn from how you tackle scale and consistency in your stacks.
Drop a comment and say hi—what's the most interesting architectural rabbit hole you fell into recently?
Hey devs — I've been deep in the agent rabbit hole lately and figured it's time to actually talk to other people building in this space instead of just reading docs in isolation.
I'm exploring how local AI agents discover and use external capabilities at runtime — things like pulling live data, extracting web content, verifying emails, generating media, or running security checks. The part that fascinates me isn't the model intelligence side; it's the infrastructure question: once an agent realizes it needs something it doesn't have, what happens next?
Right now I'm experimenting with agent service marketplaces, MCP-based tool layers, and on-demand capability access. I've been testing with Anvita Flow, OpenClaw, and a few other setups. Happy to share what I've learned so far, and even happier to hear what you're working on.
If you're building agents, thinking about agent infrastructure, or just curious about where this is all heading — drop a comment. What's the hardest part of your agent workflow right now? What breaks most often?
Hello everyone!
I’m from Malaysia and I joined DEV back in 2020, but honestly, I haven’t been very active here. 😅
I’m a software developer, mainly working with mobile apps and currently exploring more AI-related projects. I’m hoping to become more active on DEV, share what I learn, and connect with other developers from around the world.
Nice to meet you all!
Hello Dev community! 👋
I'm Victor, a startup CTO and software engineer based in Brazil.
I've been building web applications and API architectures for years, and I joined Dev.to to connect with other devs, share technical insights, and learn from this awesome community.
🛠️ My Current Tech Stack & Focus:
uv), FastAPI, SQLAlchemy, and Postgres-backed task queues.Looking forward to participating in discussions around system design, backend performance, and modern web stacks.
Excited to connect with everyone here! 🚀
Hey Victor! 👋 Welcome to DEV!
Your tech stack and focus on scalable backend systems sound really interesting! Love the combination of FastAPI, PostgreSQL, and AI integrations. Excited to see what you're building and learn from your technical insights. Looking forward to connecting! 🚀
Hey everyone 👋
I'm Advik — been building CircuitForge, a free 3D circuit simulator that runs in the browser (React, Three.js, TypeScript). Started it because I wanted a better way to learn circuits myself, so I'm learning electronics and writing about it as I go.
Been lurking and commenting around here the past couple weeks, figured it was time to actually say hi properly. Looking forward to being part of the community.
Hey Advik! 👋 Welcome to DEV!
CircuitForge sounds like such a cool project! A 3D circuit simulator built with React and Three.js is a really interesting way to learn electronics. Love the idea of learning by building something useful. Excited to see what you create and share next! 🚀
Hey! I'm Tejas, moving from Systems Engineer into Cloud/DevOps and AI, documenting the whole thing here as I go, 50+ posts in so far, mostly hands-on AWS labs and what breaks along the way.
Fun fact: I once gave up on VPC networking entirely, went and learned networking fundamentals from scratch, then came back and it finally clicked. Glad to be here 👋
The "give up, go learn the fundamentals, come back and it clicks" loop is such an underrated part of learning infra — most people either power through with half-understanding or quit entirely, so respect for actually circling back.
VPC networking specifically is a good example of where the AWS abstraction almost works against you at first — subnets, route tables, and NAT gateways make a lot more sense once you've internalized basic networking (CIDR blocks, routing, NAT itself) rather than treating them as AWS-specific concepts to memorize.
50+ hands-on posts documenting what actually breaks is a genuinely useful body of work — that's usually more valuable than polished tutorials, since "here's what broke and why" is exactly what people are searching for when they hit the same wall. Following to see what else trips you up 😄
*YOHOHOHOHO *
Hello All 😎
Creator X here unfortunately i cant remember my old account details or don't have access to the old email address but its okay ill start fresh. My name is Creator Xi a small time developer and creator.
Majority of the time a breaker of code, in hopes that the broken code works eventually. Its always awesome to see all your projects and what everyone is working on. And I hope i get to learn a lot from all of you always.
Anyway yall take it easy and once again yahooooo!
Ciao a tutti! 👋
Mi chiamo Antonio e sono felice di far parte di questa community!
Sto sviluppando BeeEngine, una libreria 2D in Vanilla JavaScript (ES6) per HTML5 Canvas, creata da zero senza dipendenze esterne per essere il più leggera e veloce possibile. Oltre allo sviluppo del motore, gestisco un portale di giochi e pubblico i pacchetti direttamente su NPM.
Mi sono iscritto su DEV.to per condividere l'architettura del mio motore, pubblicare la documentazione tecnica dei vari moduli e confrontarmi con altri sviluppatori.
Un saluto a tutti e felice di fare la vostra conoscenza! 🚀
Hi everyone! I'm Chemael, a developer building ToolZip — a collection of 48 free browser-based tools for image, video, PDF, and developer utilities.
Everything runs client-side with no file uploads. Happy to be here!
toolzip.app
Hey Chemael! 👋 Welcome to DEV!
ToolZip sounds like such a cool project! 48 free browser-based tools, especially with everything running client-side, is really impressive. Excited to explore what you've built and see what you share next. All the best!
Hey all — I'm Ryan, solo founder of Pocket Core AI. I got tired of paying for ChatGPT Plus, ElevenLabs, and Midjourney separately, so I built an offline AI app that runs entirely off a USB drive — chat, image generation, and voice cloning, no subscription, no cloud, no data leaving your machine. Turns out a chunk of the people who actually need that found it more useful than I expected. I'm here mostly to write about what I'm learning building and marketing this solo. Fun fact: I'm building this from South Africa, so half my "go check the dashboard" moments happen at 6am before the US wakes up.
Hey Ryan! 👋 Welcome to DEV!
Pocket Core AI sounds like such a cool and ambitious project! An offline AI app running entirely from a USB drive is a really interesting idea. Excited to see how you build and grow it as a solo founder. Looking forward to learning from your journey! 🚀
Hello Community,
So recently I stumbled across a problem during my work in a specific domain w.r.t performance testing. I resolved it and now would like to publish a blog and share my observations. hope it helps someone out there hitting a wall. Thanks
Hey Harsh! 👋 Welcome to DEV!
It's great that you turned a real performance testing problem into something you can share with the community. Looking forward to reading your blog and learning from your experience. Hope it helps many developers facing similar challenges! 🚀
Hello from Thailand 👋
I build developer tooling, mostly around what coding agents send out to a model and what they forget between sessions. Most of what I learn comes from things breaking in ways I did not predict — this week it was a credential redactor that caught
passwordand walked straight past the Thai, Chinese, Korean and Arabic spellings of the same word. It had been doing that for months and every test I had was written in English.That is the sort of thing I like reading about, so that is mostly what I write about: the measurement that turned out to be wrong, and what it cost.
A couple of things I am chewing on at the moment, in case anyone here has been down these roads:
Happy to swap notes with anyone working on agents, context cost, or secret handling. I read more than I post, but I do answer. Nice to meet you all.
The English-only test suite is painfully familiar. I ship a build gate that fails CI if our marketing copy makes a forbidden compliance claim, and the first version stripped HTML comments line by line to skip them.
Then someone wrote a multi-line comment quoting the banned phrases as a warning, and the check tripped on its own documentation. Same root as your redactor: my check knew the input I imagined and nothing about the input I didn't.
On your platform question, the thing that catches a Python assumption for me before CI is running the suite once under a deliberately hostile local setup: a working directory with a space and a non-ASCII character in it, LANG set to something that isn't UTF-8, and the clock in a non-UTC zone. Most of my "works on Linux, breaks on a colleague's Windows" bugs turn out to be a path, an encoding or a timezone assumption rather than a real platform difference. Cheaper to find at my desk than in the CI matrix.
Hey everyone 👋
I’m Femi. I build developer tools, and I just joined DEV.
Lately I’ve been working on Penv: schema-first secrets tooling for humans and coding agents. The short version is that
.envis still the interchange format most of us use, but it was never designed for agents that cancatthe file, scrape process output, or copy keys into chat history.Penv sits between your
.envand everything that wants to read it. It validates, types, and makes the local workflow safer before you ever need a cloud account.I’ll be sharing notes on:
.env.schemaas a shared dialectIf you’re working on env tooling, secrets, or agent safety, say hi. I’m here to learn as much as to ship.
Hey Femi! 👋 Welcome to DEV!
Penv sounds like such a useful project! Love the idea of making secrets management safer for developers and AI coding agents. The focus on keeping secrets out of chat history is especially interesting. Excited to see what you build and learn from your posts! 🚀
Hello all. I'm Rob. I build OSPulse at Fortitude Omnis Group Ltd, a small indie company taking on the VC-funded supply-chain names (Snyk, Sonatype, Socket) with no funding and no sales team! The product page is the whole pitch.
What it does: most dependency tools wait for a CVE. I care about the window before one exists, where a package changes hands, an npm account gets hijacked, or a maintainer quietly burns out. event-stream, ua-parser-js, polyfill.io and xz all showed their signs at the source weeks or months before anyone assigned a number. So OSPulse scores project health, maintainer churn, commit-velocity collapse, ownership changes, instead of the length of a vulnerability list. It ingests more than ten feeds, and I'll tell you which detections it misses as readily as the ones it catches.
On the R&D side, the piece I'm proudest of is PoisonBox. Every npm install detonates in its own disposable microVM with hardware-level isolation. It boots, does its worst, and is deleted, so nothing it does touches your machine or your keys. Underneath, an eBPF probe in the kernel logs every process spawned, file opened, secret read and outbound connection, from below the code where the package can't hide. It then draws the causal thread from the instant a package reads your npm token to the connection that carried it off. With malicious packages the hard part is proving exactly what happened and in what order, and that trace is how.
A confession, since honesty is about the only thing separating a security tool from its own marketing. Our checkout showed £249 a month while Stripe was quietly set to take £2,988 in a single hit, a figure that appeared nowhere in the journey. Two systems each holding a correct version of the same number, disagreeing only at the instant of the charge, the one moment the website never sees. It's fixed now (the price is one constant everything derives from, with a test that fails the build if the disclosure ever drops off the page), and it was caught before a single customer paid, which is the only reason I get to tell it as a story instead of a refund.
We do other technically involved things particularly around AI, Inference & LLMs. Check us out!
Anyway, great to meet you all.
Hi everyone — I’m Raju. I work mostly on TypeScript, testing, and production AI tooling. Lately I’ve been building agent-inspect, a local-first way to turn agent runs and tool calls into readable execution trees and deterministic checks. I’d especially enjoy comparing notes with people working on MCP, agent reliability, or observability: what has been the hardest failure to reproduce in an agent workflow you’ve built?
Deterministic checks over agent runs is a good hill to build on. Hardest one for me to reproduce: exactly-once alerting. I build the alerting side of a supply-chain monitor. The detector re-runs hourly and re-finds the same things, so each alert is keyed on (tenant, finding, trigger) to avoid firing the same one twelve times a day. The failure only shows up across a state change: a package already flagged for a critical CVE later turns up in CISA's KEV catalogue, which is a new event, not a duplicate, and the naive "have we sent this before?" check swallows the single most urgent alert I've got. Miserable to reproduce, because it needs the finding to exist, get sent, then escalate, in that order, across two hourly runs. It never showed up in a single-run test. How are you handling nondeterminism in agent-inspect, replaying recorded runs or pinning the model and tools so a check means the same thing twice?
Hey Everyone! I'm Sanidhya from MLH
Excited to join the DEV community. I am a Hackathon Community Manager for Asia-Pacific for Major League Hacking. Previous to which, I worked as a Backend and DevOps Engineer at a fintech startup and was also an MLH Coach.
You can find my intro post here
Excited to connect with everyone!
Hey Sanidhya! Welcome to DEV! 👋
MLH Community Manager for Asia-Pacific sounds like an amazing role! Your journey from Backend and DevOps Engineering to hackathon community building is really inspiring. Looking forward to connecting and learning from your experiences. All the best! 🚀
Hey everyone! 👋
I'm a full-stack developer with a frontend focus, mostly working with React, Next.js, TypeScript, and Web3.
I like building small tools, experimenting with AI, and making fun side projects whenever an idea catches my attention.
I'm here to discover what other developers are building, learn new things, and hopefully share some of my own projects too.
Nice to meet you all!
Hey Jay! 👋 Welcome to DEV!
Your work with React, Next.js, TypeScript, and Web3 sounds really exciting! Love the idea of building small tools and experimenting with AI. Looking forward to seeing what you build and learning from your projects. All the best! 🚀
Hi everyone! I’m glad to join this community. I’m working on 3D scanning and figure photography with motorized rotating turntables. Looking forward to sharing my work and exchanging ideas with all of you.
Hey Bertha! 👋 Welcome to DEV!
3D scanning and figure photography with motorized rotating turntables sounds so interesting! Really excited to see your work and learn more about this fascinating field. Looking forward to your future posts!
Hi everyone 😀
A big welcome to all the new members, and welcome back to everyone who is returning. It is so nice to have you all here. I hope you have a great time, make some meaningful connections, learn lots of new things, and enjoy every step of your journey.
Looking forward to seeing you around and chatting with you in the comments. Wishing you all the very best, and I hope you enjoy being part of this wonderful community 💙
Hey everyone!
I'm Sumukh, working on backend and infra systems, mostly around cloud and GPU compute these days. Landed here because I kept ending up on dev.to articles while debugging random infra problems, and figured I should actually start writing some of what I learn instead of just lurking.
Currently digging into GPU orchestration and making ML workloads less painful to run at scale. Always up for talking infra, DevOps, or anything cloud-related. Feel free to say hi!
Fun fact: I can solve a Rubik's cube in under a minute, but I still can't parallel park on the first try. 😅
U.S. Business Partnership Opportunity
We’re a Japan-based software development team looking to build a long-term partnership with a reliable U.S.-based professional.
Our team handles the technical side—from development and testing to project delivery. We’re looking for a U.S. partner who can help with client communication, business coordination, and developing new opportunities in the U.S. market.
This is a revenue-sharing partnership, not a traditional employment position. Partners can receive 30–35% of the agreed revenue/profit share, depending on the project and responsibilities.
If you’re interested in technology, freelancing, or building a side business and would like to learn more, send me a DM. I can provide the details, expectations, and example project structure.
Hello dev.to community!
I’m a Systems Engineer. I joined dev.to to share practical insights on infrastructure and system operations, and to learn from the perspectives of developers. I’m excited to connect with everyone!
Herkese merhaba, ben Mehmet Amed Ürey. Dev.to topluluğuna hem projelerimde öğrendiklerimi ve tecrübelerimi paylaşmak hem de yeni araştırmalar yapıp farklı alanlarda bilgi edinmek için katıldım. Burada olmak harika, herkese keyifli kodlamalar!
hey everyone 👋 i'm eru. i built Empryo solo because i kept getting frustrated with token usage and having to explain the same codebase to my agent over and over.
i'm working on a living project map i call the Genome, plus a desktop app and TUI. also gave the little agent themes and some life because i wanted it to be fun to use lol.
i'd love to meet people working on coding agents, or people tired of burning through their subscription or credits after a few prompts. what eats yours fastest? repeated repo reads, retries, long tool output, or something else? and how are you keeping project context between sessions?
i'll be sharing what i'm building and learning here. happy to be here!
Hi everyone! I’m building Plembfin, a self-hosted watch-history and playstate sync hub for Plex, Emby, Jellyfin, and Trakt. I’m here to learn, share progress, and connect around open source, architecture, and reliable integrations.
Hello. My name is Dan. I have been working for 15 months on something and now I get the luxury of getting to share it now that it is done. My main focus is always on research and how things should work, not how they work. I am not into social media online really, but I do believe in engineering and mathmetics so, eventually, I had to come to terms with my meathead persona and give it a real go. I try to be nice, but I want to be honest. I am not really a nice person, but you bet your bottom dollar I am working for a better tomorrow and not going to sit idled while the planet gets destroyed for some crazy people talking about conscious AI and brainwashing people to believe that they have lost control of AI while they pump youtube full of money towards people who will spread fomo. It is disturbing and I built the alternative. Not like I will. No. I built it already. All the work is here zenodo.org/communities/pi_origin_architecture. I am always open to talking. I am not into small talk.
Hi, I’m Isha, a senior software engineer with 5+ years of experience, primarily focused on backend development. I work with Go and Python, along with REST APIs, gRPC, and distributed systems. I enjoy solving complex technical problems, improving system reliability, and exploring AI and LLM based applications.
Hi everyone! I'm Ganesan, building Plumloom Autoeval, an open-source CLI for evaluating LLM and AI agent outputs before they ship. It measures whether an eval score is reliable or just run-to-run noise, so teams can gate releases on evidence they trust. Runs from the terminal, CI, or coding agents like Claude Code and Codex.
Happy to be here!
GitHub Repo
Hey everyone! I'm Daniyal solo founder building XenorAI under my studio DevXcript. Working on an AI sales agent for websites that scores leads and tells businesses why visitors don't convert. Excited to be here and learn from other builders.
Hi all. I'm a backend engineer in Australia, mostly payments and infra by day I joined mainly to read up tech war stories and read what other people are doing. If anyone here has fought with pdf.js or WASM in a strict CSP, I'd love to compare notes.
Olá, pessoal! 👋
Estou cursando Análise e Desenvolvimento de Sistemas (ADS) e atualmente estou no 2º semestre. Ainda sou iniciante na área, mas estou buscando aprender cada vez mais sobre programação e desenvolvimento.
Estou começando essa jornada para evoluir meus conhecimentos, conhecer novas tecnologias e, principalmente, colocar o que aprendo em prática.
Hello DEV! 👋 Just joined, thought I'd say hi!
Hey everyone,
After lurking around this awesome community for a while, I figured it was finally time to step out of the shadows, introduce myself, and hopefully make some new tech friends.
My name is Rakesh. By day, I’m a frontend engineer with about 11+ years of experience under my belt. I've spent over a decade wrestling with CSS layouts, optimizing JavaScript bundles, and architecting UIs. Over the years, I've worked across various frontend frameworks, with a heavy focus and deep expertise in React.
I love the visual and interactive side of web development, but lately, I’ve been feeling that itch to learn something completely outside my comfort zone.
So, I’m officially embarking on a new chapter! 🚀
Right now, I am deep-diving into Python with the ultimate goal of transitioning into AI Engineering. It feels incredibly exciting (and a little humbling) to feel like a beginner again after so many years in the frontend ecosystem.
What I’m hoping to do here:
If you have any recommendations for great Python libraries, machine learning roadmaps, or must-read AI blogs, please drop them in the comments below.
Looking forward to connecting with you all! 🥂
Hi dev.to.
I'm not a computer science person. I studied urban planning, now learning public management. Somewhere along the way I got curious about code, AI agents, and how memory works across sessions.
So I've been teaching myself — Python, JavaScript, AI agent, and whatever else catches my attention. I like learning and exploring, even when it's slow. I'm not in a hurry.
I joined here to meet people, share what I'm figuring out, and grow alongside others.
Glad to be here. 👋
Hi all, backend dev from Pakistan, mostly Java and Spring Boot. I work on payment systems, integrations, and on SaaS products, so I spend a lot of time on retries, timeouts, and bugs. Planning to write about that here.
Hey everyone!
I'm interested in AI and always curious to learn more. I'm currently exploring different ideas and building things to understand them better. I hope to share what I learn here and hear from others on similar journeys.
Looking forward to being part of this community.
Thanks for reading!
Hi and Welcome! Glad to have you here!
Hello everyone!
I’m Aly, an SEO Specialist at Web Designer Orange County. I’m excited to join the DEV Community, learn from others, and connect with people passionate about technology and the web.
I’m interested in*_ SEO, technical SEO, web development, WordPress, and website optimization_*. Looking forward to sharing ideas, joining discussions, and learning from the community.
Happy to be here!
Hi everyone!
I'm Uthaya Kumar, a web developer and AI automation enthusiast from India.
I mainly work with WordPress, WooCommerce, HTML, CSS, JavaScript, and n8n. Recently I've also been spending more time exploring AI automation, APIs, and practical AI workflows for businesses.
I'm here to learn from other developers, share things I build, and connect with people working on interesting projects.
I recently published my first DEV article about building a responsive business landing page with HTML, Tailwind CSS, and GitHub Pages.
Looking forward to being part of the DEV community!
Hello everyone! 👋
I’m so excited to finally join the DEV Community! I’m a web developer who loves building, experimenting, and exploring ways to make the web faster and more private.
Lately, I've been diving deep into native browser APIs (like Web Crypto and Intl.Segmenter) and just finished building a suite of 100% client-side developer tools. I’m here to learn from all the amazing experiences people share, discover new trends, and connect with devs who love clean, serverless architecture.
Looking forward to reading your articles, sharing what I learn, and contributing to the discussions!
Happy to be part of this awesome community! 🚀
Hi everyone! I'm MohammadAmin. I'm a Linux enthusiast, web developer, and the founder of a cybersecurity platform called HackTube. I joined the DEV community to share my experiences with system administration, configuring secure networks, and building robust backends with Django.
I'm really excited to connect with other developers, read your articles, and start sharing some of my own technical guides soon! 🚀
Hi everyone !
i am Hadiqa , I joined this community to learn from other developers, explore new technologies, work on interesting projects, and connect with like-minded people. Looking forward to learning and contributing here!
Nice to meet you all!
Hi everyone! 👋
I'm Dmitriy, creator of the Import Export by RockStarLab WordPress plugin. I build solutions to help developers streamline site migrations and content deployment.
Glad to join the DEV community and connect with fellow developers!
Hey everyone! 👋
I’m an SRE based in Canada and love to connect with folks wrestling with distributed systems at scale, talk operational reliability, and learn how others are bringing reliability into production without breaking their core uptime guarantees.
Excited to join the community and chat all things backend architecture and observability!
same here
Hi mọi người! 👋
Mình đang xây dựng PionPay — một giải pháp xác nhận thanh toán tự động bằng API cho các startup và doanh nghiệp kinh doanh dịch vụ số tại Việt Nam. Mình tham gia DEV để học hỏi thêm về cách các dev khác xử lý bài toán tích hợp thanh toán, bảo mật API, và cũng để chia sẻ lại những gì team mình đúc kết được trong quá trình xây sản phẩm.
Đang học thêm về content strategy cho sản phẩm B2B tech, và khá thích đọc case study thực chiến hơn là lý thuyết suông.
Hi everyone! Stella here 👋 Non-technical person who somehow wandered into AI and decided to stay. My path so far: AI image generation-AI short dramas -marketing & ops for an LLM aggregation platform - now in AI infra. Stumbled onto DEV and it feels like a goldmine. My goal here is simple: finally learn to code properly and figure out how to use AI tools beyond just prompting. Looking forward to learning from you all — thanks for having me!
Hi everyone 👋
I’m Mykhailo, a PHP/Laravel developer from Ukraine, currently based in Montenegro.
I’ve been working with PHP for years and lately I’ve been building my own products, including PHP Ukraine, a platform for PHP developers and jobs.
I joined DEV to share some real engineering notes from the projects I’m building and to connect with other developers.
Glad to be here!
Hi everyone! 👋
I'm building PionPay.vn — an automated payment confirmation solution via API for startups and digital service businesses in Vietnam. I joined DEV to learn how other devs handle payment integration and API security challenges, and to share what our team has picked up along the way building the product.
Currently diving deeper into content strategy for B2B tech products — I tend to enjoy real case studies more than theory.
Fun fact: PionPay just earned our ISO/IEC 27001:2022 certification — the whole team celebrated with a... longer than usual code review session 😄
Looking forward to connecting with all of you here!
Hey everyone! I’m Fran from Spain. I’ve been a developer for over 12 years and I’ve just discovered this community. There’s clearly a lot of talent around here, so I hope I can live up to the level!
I’m not much of a writer and I probably won’t have a huge amount to contribute, but I’ve learned quite a lot along the way and I hope I can be helpful in some way.
Have a fantastic day!
Hello DEV Community! 👋
I’m Gabriel, a full-stack developer from Ghana working with Angular, React, TypeScript, Node.js and MongoDB.
I’m currently building OrderBridge AI, a WhatsApp ordering assistant designed to help restaurants manage customer conversations and orders more efficiently.
I joined DEV to deepen my knowledge of software engineering and system design, share lessons from building real products, ask better technical questions and learn from experienced developers.
I’m looking forward to connecting, learning and contributing to the community!
Hello everyone!
I’m Jennifer, a software engineer who likes building tools around the little inefficiencies that start getting annoying after the third time.
Right now, I’m spending a lot of time on GitHub automation and developer tooling. One of my projects is AppFactory Project Automation, a reusable GitHub Action that helps set up and keep GitHub Projects, issues, backlog metadata, and pull request workflows in sync.
I joined DEV to share what I’m building, what worked, what didn’t, and the small technical problems that pushed me to build these tools in the first place. I’m also here to see how other developers solve similar problems, especially when their approach is completely different from mine.
I’m into open source, DevOps, automation, security, and software engineering in general.
Happy to be here 🫠
Hi Everyone.
I’m Hardik, excited to be joining the DEV Community. I’m here to learn, share ideas, and connect with people who enjoy building, experimenting, and exploring technology.
Happy to be part of this community, looking forward to connecting with you all! 🚀
Hi everyone! I'm Pando, from France.
I'm not a developer by training — I come from technical sales. Over the past year I learned to build apps with AI coding agents, and I shipped a full SaaS to production on my own: auth, Stripe payments, database security, deployment, backups.
What surprised me most: the AI writes the code well, but nobody warns you about what happens after. I'm here to write about those production pitfalls, the ones that cost me weeks.
Fun fact: I once spent three weeks debugging "regressions" that didn't exist. It was a service worker serving an old cached version of my app. More on that soon!
Hey, I'm Mark and I'm learning "Web Development" at the moment (Soon learning JavaScript/React/SQL/...). I already learned JAVA. I plan to make a fullstack game or a project to test my knowledge. I'm a passionate learner - I love things about how to utilise your time to the MAX, control your distractions, learning techniques and about self improvement stuff. If you're interested in talking about anything or programming together - simply message me 'hello, let's build something' or 'wanna talk about deep work?' <3
Hi Everyone! I am a Senior Software Engineer at Plunes HealthCare, building AI-driven tools and scalable full-stack systems.
I'm here to learn from the community, share what I'm building, and connect with other developers. 🚀
Looking forward to learning and connecting with everyone here!
Hey, I'm Aditya — a first-year Data Science student in the IIT Madras BS Program and a self-taught developer.
I recently published a cryptographic file encryption library called GUN101 on PyPI. Professional cryptographers on Security Stack Exchange reviewed it, found real issues, and I fixed everything and documented the whole process publicly. That write-up is coming soon here on dev.to.
If you're into Python, security, or open source — I'd love to connect. Always looking for feedback and contributors.
github.com/dialga-cmd
Hi everyone. I make animated explainers about mechanisms every developer runs into - the event loop, floating point, Git objects, regex backtracking. The one rule I hold myself to: every number in them comes out of a script that ran, not out of memory.
Just published my first article here, on what a commit actually stores and why git gc does not remove a committed secret. It ships with the script that reproduces every number in it, so if one comes out different on your machine I would rather hear about it than not.
Glad to be here.
Hi everyone! I’m happy to join you 😊 I enjoy learning new things, challenging myself, and testing my skills. I already know how to do many things, but there’s still a lot I’d like to learn and improve!
Hey everyone 👋
I’m an Immunefi whitehat, hackathon builder, and solo developer currently working on FailEcho, a shared failure intelligence network for AI agents.
I spend most of my time around AI agents, MCP, security, reverse engineering, Linux, and reliability infrastructure.
I’m here to learn from other builders, share what I’m working on and see what breaks in real world agent systems.
If you’re building agents or MCP tools, what failure do you keep seeing over and over?
Hello everyone! I'm currently developing YottaCode and spending my days hacking on coding agents.If anyone else here is building in the AI/Agentic space, working on developer tools, or just loves deep-diving into automation, I'd love to connect! Looking forward to sharing some of our engineering insights and learning from the community here.
Hi! I'm building AI agentic systems right now and would love to share!
Hi HN, I'm Sergio, a junior dev from Spain. I built D-Engine because I was burning through API credits driving coding agents.
The idea: the LLM only proposes SEARCH/REPLACE blocks. A deterministic local runtime applies them in an isolated git worktree, runs tsc --noEmit, and only merges if compilation passes. No agentic loop re-sending the trajectory every turn.
I ran a reproducible 10-task benchmark against DeepSeek's own harness (same model, same prompts): ~42× fewer tokens, tied quality (48/50 vs 48/50). Methodology, raw data, and honest limitations are in the repo — including the tasks where agents do better than my tool.
Happy to answer anything.
Hey everyone, I’m Robin J. 👋
I build small web tools and usually end up spending more time on the weird edge cases than the original feature.
Most of what I work with is JavaScript, TypeScript, React, APIs, Cloudflare, Linux, and backend infrastructure. Right now I’m working on a small project called IGPuller, and it has already sent me down a few rabbit holes around URL handling, media parsing, rate limits, and keeping things working when the upstream platform changes.
I joined DEV mostly to read what other people are building, share a few things I learn along the way, and hopefully pick up some better ideas from people who have already hit the same problems.
Glad to be here.
Hey all 👋 I'm Ricardas, a Senior Fullstack Engineer.
I am a bit of clean code freak, started investing time in code quality tools, to help the community and your AI agents to write clean code (not on prayers and hopes, but on enforced rules :)). Also spend a fair amount of time building tooling around AI-assisted development (agent workflows, MCP servers) rather than just using it as-is.
Looking forward to reading through the community's posts and swapping notes!
Hey DEV 👋
I'm Vinayak, a CS student from India. Currently learning AIML and DSA.
I made this account to write about what I'm learning, mostly the stuff I get stuck on and how I figure it out. Figured writing it down might help someone else running into the same thing.
Open to suggestions on what to write about. See you around!
Hey Vinayak! 👋 Welcome to DEV!
I'm also a recent joiner here, looking forward to learning, sharing, and connecting with fellow developers. Excited to read your blogs and learn together. All the best! 🚀
Hi everyone,
I'm João Pedro, a full-stack developer based in Goiânia, Brazil, with about
5 years building systems for real businesses: a WhatsApp-based CRM with an
AI layer, a platform for a taekwondo federation, a multi-tenant voting
system, a self-hosted classroom platform, a referral system with commission
tracking.
A few things about how I work:
Stack I use most: TypeScript, Python (Django/DRF, FastAPI), Next.js, Astro,
PostgreSQL.
I just finished writing up six of these projects as full case studies:
architecture, decisions with their accepted cost, invariants, and a real
incident each one had, not a hypothetical. It's at joaoborba.dev, in English
and Portuguese, if you want to see how the sausage gets made.
I'm looking for remote opportunities, ideally with teams in North America or
Western Europe. Happy to talk shop about any of this: decisions, incidents,
or the trade-offs nobody puts in the readme.
Looking forward to being part of this community.
Hey! I’m Mika!
I’ve been teaching myself more Linux/software development, while most of my recent rabbit holes have involved Python, GTK4, GNOME, Wayland/XWayland.
I’m currently working toward Mochi’s first public alpha and just started writing about what I’m learning along the way. Excited to meet other Linux/Python/desktop devs here! 🌱
Hi everyone 👋
I’m Sam, from India. I’m currently building YBS — Your Browser Suite, a collection of practical browser tools for developers.
I’m here to learn more about web development, share what I learn while building, and connect with other developers. I recently started writing about topics like Unix timestamps, cron expressions, and developer utilities.
Looking forward to learning from the community and contributing where I can. 🚀
Hey everyone! 👋
I'm Hamza Sajid, an Agentic AI Engineer & Software Engineer based in Pakistan.
I specialize in building production-grade autonomous AI systems—focusing on OpenAI Agents SDK, Model Context Protocol (MCP), and multi-agent swarms.
💡 What brought me here: I joined DEV to share deep-dive field notes on agent architecture, context engineering, and harness design—and to connect with developers building in the AI & full-stack space.
🛠️ What I'm currently working on: Architecting persistent AI Workers (Digital FTEs) and sandboxed MCP tool servers for real-world enterprise operations.
Looking forward to connecting and exchanging ideas with everyone! Feel free to say hi or check out my writing at hamzasajid.netlify.app.