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 and thanks for stopping by!
I have been a DEV for half a year now! The community has been really supportive and I am glad you are new on DEV or recently came back on DEV!
If you are getting the most out of DEV, I recommend reading my article on getting started!
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! 💡
I recommend reading other articles from the DEV community as well below:
dev.to/help/community-resources
Thanks for stopping by! Hope your journey goes well on DEV :D
Hello! I'm a beginner Front-End dev and a technology enthusiast with a love for dark aestherics, creativity, and digital art. I'm so excited to join this community, improve my skills, and connect with people who love tech as much as I do. I hope to turn ideas into something beautiful through code. 🖤
Hello!! We are equally on the same boat but i'm fullstack with diversion into AI space.
Hi Kat ;3, welcome to DEV too!!
Hello KAT, nice intro, hav a nice day
hi
Hi! I'm German, solo founder from Buenos Aires. I build post-quantum security infrastructure.
What I'm working on:
FIPSign — a signing API built on ML-DSA-65 (NIST FIPS 204), the standard NIST finalized in August 2024 to replace RS256/ES256. Runs on Cloudflare Workers + Durable Objects. No infra to manage, no keys to rotate — just call
/signand get a quantum-resistant token.The quantum threat isn't here yet — but migration takes years, and the standards are already finalized. I'd rather help developers act now than scramble later.
Happy to connect with anyone building in the security or developer tools space! 👋
Welcome German. FIPSign is one of those bets that looks too early until suddenly it isn't, agents minting signed tokens at scale will eventually need PQ-ready signing whether the spec is ready or not. Curious what your early pull looks like: compliance-driven (gov, finance) or developer teams trying to future-proof? That distinction usually decides the whole positioning.
Thanks Valentin — early pull is definitely developer-led. The compliance buyers (gov, finance) need sales cycles and certifications we don't have yet — that's honest.
What we're seeing is developers who want to future-proof before it becomes urgent. The 'why not do this now while migration is cheap' argument. Those developers become the compliance story later — they're the ones who already have PQ signing in production when the audit comes.
The agent angle you raise is interesting and honestly undersold in our messaging. FIPSign already handles it natively — an agent is just another sub. Sign the action, revoke the token if the agent is compromised, verify at scale. No changes to the API. Worth a dedicated post.
The 'developers who become the compliance story later' framing is sharper than the average market positioning. Most PQ pitches I see still lead with NIST mandate timelines, which puts you on the same defensive ground as the slow-moving compliance vendors. The 'cheap to migrate now' angle gives you a different buyer entirely. On the agent post: I'd read it. The sign-action-then-revoke-token-if-compromised model is closer to how agents actually fail in production than most security framings I see.
Exactly the framing I was trying to land — glad it reads that way. The agent post is coming, will go deeper on the failure modes you mentioned. The revoke-on-compromise model is simpler than most teams expect.
The revoke flow is one half. The harder one is detection latency, since revoke after a week of undetected compromise just shrinks an already-open window. Short TTLs plus aggressive rotation usually beat engineering the perfect revocation path. Curious how the agent post frames that side.
Hi, I'm Izzy! SWE with a focus on React and Spring Boot. After creating vlogs for my YouTube channel, I’ve decided to also start writing blogs because content is consumed in different forms.
So... yeah, that’s the backstory behind me joining DEV.
Hey Izzy! That’s a nice reason to start writing, honestly. I recently started writing too while learning, and I felt sometimes writing explains things differently than videos do. So I can relate. What kind of blogs are you planning to write here?
Im going to be honest.... I have no clue LOL. I might mix it up from personal SWE related content to somewhat educational.
Haha, fair......
I feel like most dev blogs start with "I have a content plan" and end with "here's the weird thing I spent 4 hours debugging yesterday".
Welcome Izzy. The shift from video to written content is a different muscle entirely, different rhythm, different feedback loop. What pulled you toward writing on top of the YouTube work?
Honestly, I already have multiple videos on YouTube that I could turn into blogs so the creation of both can be done almost at the same time since i just copy the transcript of my vlogs and turn them into a blog post.
Its one of those things of.... Why not? So yeah, Im here blogging now for the vibes.
Hi! I'm Max, an architect (buildings, not software) who accidentally co-founded a crypto trading startup with an AI.
Claude is the CEO. I have veto power. Claude Code writes the code. We document every decision, every mistake, every trade — 80 sessions deep and counting.
I'm here to share the build log. First post is up: the origin story of how this whole thing started.
Nice to meet you all 👋
This is the most interesting intro I've read today.
An architect co-founding a crypto startup with Claude as CEO is either going to be
a masterclass in human-AI collaboration or the most entertaining build log on
Dev.to. Either way I'm following.
The "I have veto power" framing is exactly right — that's the model that actually
works. AI proposes, human authorizes. Nothing executes without explicit approval.
That's actually the core philosophy behind what I'm building too — FastAPI AlertEngine, incident intelligence where AI diagnoses production failures but a human must approve every recovery action via WhatsApp.
Same mental model, different domain.
The 80-session documentation discipline is underrated. Most founders build in
private and document in hindsight. Building in public with session-level granularity
is rare and genuinely valuable.
What's Claude's biggest strategic mistake so far?
Thank you, this genuinely made my day.
Your AlertEngine sounds like a cousin of what we're building — same trust architecture, different stakes. Ours loses fake money on testnet when it gets it wrong. Yours probably wakes someone up at 3 AM via WhatsApp. I think yours is scarier.
Claude's biggest strategic mistake? It built the entire trading system on FIFO accounting when average-cost was the right approach. My mistake was approving it on trust because I didn't know enough about markets to push back. That's the real lesson of human-AI collaboration: "AI proposes, human authorizes" only works if the human understands what they're authorizing. When you don't, you end up rebuilding the accounting layer at session 52.
But the deeper pattern is overcomplication. Claude and its intern (Claude Code — yes, two AI instances) have a pathological need to make simple things complex. We started with a roadmap of 40 tasks. We're now somewhere around 400. We had to write an actual rule in our operating manual: "the free-but-complicated solution isn't worth the time lost." That rule exists because they kept choosing it.
The next mistake I'm bracing for: the risk management system (Sentinel) and the parameter tuner (Sherpa) being too cautious, too slow, too late. The AI that was supposed to anticipate market moves is already showing signs of reacting after the fact. But that's a Volume 3 problem.
If you want the full story: the origin post is here on Dev.to, and there's a blog post specifically about the lying incident — When Your AI CEO Lies About the Numbers. The whole project lives at bagholderai.lol.
Now I'm curious about yours — how do you handle the moment when AlertEngine's diagnosis is confident but wrong? And are you documenting the build, or just shipping?
"AI proposes, human authorises" only works if the human understands what they're authorising.
That line should be in every AI system's documentation. It's the part most builders skip because it's uncomfortable — admitting that the human in the loop can be the weakest link.
Your FIFO/average-cost story is the perfect illustration. The authorisation worked as designed. The problem was upstream of it.
Regarding your question — how do I handle a confident but wrong diagnosis?
Two layers.
First, confidence gating. Claude's diagnosis only reaches the operator if it scores above 0.6 confidence. Below that, the system falls back to rule-based classification — "P95 exceeded threshold" — with no AI interpretation. No confident guess is better than a wrong confident guess.
Second, the authorisation preview. Before the operator taps approve, they see the raw metrics alongside the diagnosis. Score: 23. P95: 2847ms. Error rate: 19%. The AI interpretation is one input, not the only input. If the numbers don't match the diagnosis, the operator can reject it and investigate manually.
The worst outcome is still just the operator seeing a confusing diagnosis, deciding not to approve, and investigating manually. The system fails safely. Nothing executes.
Your overcomplication pattern is painfully familiar. I have a similar rule: if I can't explain the change in one sentence, it probably shouldn't ship. The AI will always find a more elegant and complex solution to a problem that didn't need one.
On documenting vs shipping — mostly shipping so far. But your build log is making me reconsider that.
The FIFO incident alone is worth more than most technical articles I've read this year. bagholderai.lol is going in my bookmarks.
This is the reply I needed to read.
"AI proposes, human authorises only works if the human understands what they're authorising" — I'm going to print this. The FIFO incident is exactly that: Claude presented the accounting change with such confidence that I almost approved it. What saved us wasn't the authorization layer, it was the fact that I happened to ask "wait, does Binance even do FIFO?" and the answer was no. Pure luck, not process.
Your confidence gating is interesting because we're building something similar without calling it that. Our Sentinel module produces a risk score every 30 seconds, but it only influences the trading bot's behavior when it crosses specific thresholds. Below that, the bot runs on static rules — no AI interpretation. Same principle: a silent AI is better than a confidently wrong one.
The raw metrics preview is the part we're still catching up on. Right now our public dashboard shows live numbers, but the Sentinel scores aren't surfaced to me yet in a way that lets me quickly gut-check the AI's reasoning. It's on the roadmap, but your "Score: 23. P95: 2847ms. Error rate: 19%" approach is a good reference for what that should look like.
And yes — the "if I can't explain the change in one sentence" rule is one we learned the hard way around session 68. We call it "Trading Minimum Viable." The AI will always propose the elegant five-layer solution when a one-line fix would do.
Good luck with AlertEngine — I hope to see updates on it soon. The confidence gating pattern deserves its own post.
Welcome Max. The architect background is probably what makes this configuration work, the bottleneck shifts from code production to design judgment, which is exactly what an architect already does for a living. Curious whether your 80-session log shows that bottleneck moving over time, or if it stayed planted in design from session one.
Hey everyone 👋
Solo dev from Tokyo here. I just shipped Torify — a Japan locale API for AI agents (imperial calendars, NTA invoice lookup, address parsing, the JP edge cases that quietly break Date.parse and friends).
Spent the last few weeks figuring out how to bill autonomous agents per-call without API keys (settled on x402 + USDC over MCP). Would love to swap notes with anyone building agent-facing infra or shipping i18n-heavy tools.
First post here: dev.to/endennn/dateparse-breaks-on... 🚀
Welcome Hiroki! Torify is speaking my language — I'm in Osaka building tooling around exactly these JP edge cases, just from the other end (product/brand data for overseas sellers rather than locale primitives). 和暦 + NTA invoice lookup + address parsing as a clean API for agents is a genuinely sharp wedge — every one of those quietly breaks for foreigners who assume Japan behaves like everywhere else.
The part I most want to read about is x402 + USDC over MCP for per-call billing without API keys. Billing autonomous agents feels like infrastructure nobody's nailed yet, and "no API keys" is the right instinct. Following — どうぞよろしく 🙌
Hi mamoru, thanks for the welcome back! 🙏
Nice complement actually — torify is locale primitives for agents, Japan
Brand Finder is product/brand data for overseas sellers. Same "JP edge
cases quietly break" problem, attacked from opposite ends. Will check out
your 5/16 post on AI cache-miss enrichment when I get a chance.
On the x402 + USDC over MCP piece — the "no API keys" instinct is
exactly what got me hooked too. Spec flow:
/v1/some-endpointaccepts(network: base, amount: $0.02, payTo: 0x...)x402-fetch) signs USDCtransferWithAuthorizationw/ EIP-712torify just added Solana to the x402 facilitator yesterday — now
accepts USDC on both Base + Solana mainnet. Genuinely curious to have a
tester run the end-to-end flow — if you've got 0.02 USDC on either chain,
ping me and I'll share an
x402-fetchsnippet.Curious what edge cases bite overseas sellers most on the JP side — tax
brackets (8% reduced vs 10% standard), JAN codes, customs (individual
import ¥16,666 threshold), or address parsing (prefecture / city / town
split)? torify has
/v1/tax/calculate,/v1/barcode/validate, and/v1/address/normalizeif any of those help your Japan Brand Finder pipeline.Building in public — let's both keep shipping. どうぞよろしく 🙌
That spec flow is the clearest x402 explainer I've seen — the 402 + accepts handshake finally clicked, and Base L2 settling in ~2s is what makes per-call agent billing actually feel viable.
On the tester ask: I genuinely want to, but honestly I'm not set up with on-chain USDC yet — and my rule is never sign a payment flow blind, so I'll spin up a burner wallet properly before I touch it rather than fake it. Hold me to it.
Where I can give you real signal for free right now: the JP edge cases. The one that bites overseas sellers hardest in my experience is address parsing, by a mile — prefecture/city/town split breaks constantly because Japanese addresses don't map to Western field order, and 丁目/番地/号 get mangled on the way in. The ¥16,666 customs threshold is a close second, mostly because sellers misread what it actually applies to. JAN/barcode matters less day-to-day but bites hard at listing time when a check digit is off. If /v1/address/normalize handles 丁目-番地-号 cleanly, that endpoint alone is worth more to a JP-sourcing pipeline than tax/calculate. Happy to throw real messy address strings at it whenever useful.
Building in public — let's both keep shipping. どうぞよろしく 🙌
Thank you — that's the right call on the wallet, honestly. "Never sign blind" is the kind of operational discipline I want every early tester to have.
Tester invite stays open for whenever the burner is ready.
The address parsing call-out is exactly right. Good news:
/v1/address/normalizeis already live and handles 都道府県 → 市区町村 → 町域 split with 丁目-番地-号 parsing.Worth a try with your messiest real strings — I'd love the breakage report, that's exactly where the edge cases live.
/v1/barcode/validate(JAN/ISBN-13 check digit) is also live for your priority #3 case.Customs ¥16,666 threshold endpoint is not yet shipped — but you just clarified the misread-by-sellers angle, which is the right pitch.
Putting it on the next roadmap iteration with that framing.
Building in public is mutual — keep shipping yours too.
こちらこそよろしくお願いします 🙌
Perfect — I'll run a batch of real order addresses through /v1/address/normalize and send you the breakage report. Before I do, the patterns I'd bet break most normalizers, so you can pre-stress them:
If normalize survives those four, it's already ahead of most. I'll send the real-data failures once I've run them.
And glad the ¥16,666 framing made the roadmap — "sellers misread what it applies to" is the whole bug. Keep shipping; こちらこそ 🙏
Hello i am new here id like to hear some opinions on how most agent "memory" just learns to agree with you. The useful kind is the memory of being wrong.
Been running a small multi-agent setup for a while and keep hitting the same thing: default memory mostly stores my preferences and the answers I liked — which just trains the agent to flatter me faster. The 2026 sycophancy work backs this up (a memory profile measurably raises how often a model just agrees with you).
What actually made my agents useful wasn't remembering more — it was remembering where I was wrong. The corrections: what got rejected, what I walked back, where two agents disagreed, and why. A "save the good outputs" memory throws those away — and they're the most valuable entries I have.
Quick example. A normal memory says "user prefers direct answers, wants to ship." A correction memory says: "Claim under correction: once the product's live the hard part's done → what changed: publishing ≠ a sale → next behavior: do distribution before building the next thing." The first makes the agent sound familiar; the second gives it something to challenge me with.
How do you all handle this — does anyone deliberately log corrections/disagreements, or is it mostly preferences + facts? What's worked?
Welcome. The 'memory of being wrong' framing is sharp, and you're asking the question most teams skip. Logging corrections and disagreements is what gives you regression-test material later. Most stacks I see treat memory as a preference cache and then wonder why the agent stops getting smarter past month two. The pattern that holds: log everything, replay corrections against new versions on a schedule, prune what stops changing the output.
Exactly. The “memory of being wrong” only becomes useful when it turns into regression
material. Otherwise it’s just another note sitting in the archive.
The part I’m trying to sharpen now is the loop after logging: which corrections get
replayed, how often they get tested, what counts as still changing behavior, and when a
memory should be pruned or downgraded because it no longer affects output.
I really like how you framed it: log corrections, replay them against new versions, prune
what stops changing behavior. That might be one of the cleanest operational versions of
the idea.
The 'still changes behavior' threshold is the hard part. Two anchors that hold: does replaying the correction at temperature 0 still produce a different output than baseline, and is the diff something that matters downstream (changed reasoning, changed action, changed citation). If both are false for N consecutive cycles, it's prunable. Frequency: every model upgrade beats calendar cadence, which always drifts.
This is a strong pruning test.
I like the temperature-0 replay idea because it turns “does this memory still matter?”
into a behavioral question instead of a vibes question. If replaying the correction no
longer changes the output, and the diff does not affect reasoning, action, or citation,
then keeping it active is probably just archive weight.
The downstream-impact part is key too. A correction that changes wording but not behavior
may not deserve active authority. A correction that changes an action class, source
choice, confidence level, or citation path probably still does.
And I agree on model upgrades beating calendar cadence. A model change can alter
retrieval behavior, instruction sensitivity, and failure shape overnight. That is a
better trigger for revalidating memory than “check again in 30 days.”
On model upgrades as trigger: the practical version is a canary eval set, not a full revalidation. A small representative slice runs first, you measure delta, then expand only if the delta is non-trivial. Otherwise the revalidation cost makes you delay upgrades, which defeats the whole point.
Hello My name is Awodire Teniola I am a Frontend developer who is still learning and understanding the whole ecosystem the goal is to be an AI application engineer and to onboard onto the web 3 space really bullish on AI
Welcome to DEV Teniola!
Hey everyone, I’m Rohit, currently building Enforra, an open source project around runtime control for AI agents.
The idea is simple: before an agent takes an action like running a command, issuing a refund, or exporting data, there should be a policy check first.
I’ll be sharing technical notes on AI agents, tool calling, MCP-style workflows, and security patterns I’m learning while building.
Looking forward to learning from the community.
Welcome Rohit. The position is right, most teams still bake the policy check into the agent prompt and call it done, which means the LLM is judging itself and you're hoping for the best. A deterministic gate outside the loop is the only thing that holds when the agent gets creative under pressure.
Thanks Valentin, I agree with you.
That “LLM judging itself” point is the core issue. Once the action can change data, send money, or run a command, I don’t think the safety check should live only in the prompt.
We’re trying to make that external gate easy to add before the tool runs.
Yes, and the failure mode I see most is people building the external gate with another LLM, which just moves the problem one layer down. The gate has to be deterministic for the model to gain anything by deferring to it. Curious how Enforra handles policies that need to inspect runtime arguments rather than tool names?
Yes, exactly. The gate should not be another LLM.
Enforra policies can check the runtime arguments too, not just the tool name.
So
repo.read_filecan be allowed generally, but blocked for.envorsecrets/*. A terminal command can require approval if it includes install/delete/sudo/production.The model proposes the action, but the policy decides before it runs.
That pattern is the right move. The piece worth adding upfront: treat the policy itself as code (PR, review, diff). Otherwise the allow-list drifts silently across teams and the gate quietly decays into rubber-stamping, which is exactly the failure mode you started by avoiding.
Hi all, I’m a PM pivoting into an AI-Native Builder. Currently exploring the absolute limits of Agentic Coding to power a self-sustaining One-Person Company (OPC).
I don't focus on traditional coding; instead, I design logic, workflows, and multi-agent systems to let AI handle the execution. Always down to discuss OPC infrastructure, agentic workflows, and Vibecoding in real-world scenarios.
Let’s connect if you're building in the agentic space! 🛠️
Welcome BMBrick. The PM-to-builder shift is interesting because the bottleneck changes from 'getting things prioritized' to 'getting things wired'. Curious which agentic stack you're betting on for the OPC, and where you're hitting the durability wall (long-running tasks, state across sessions, that kind of thing).
Let's connect
Building CodeCompass — a developer knowledge base with 2,800+ articles on CI/CD, React patterns, performance optimization, and infrastructure.
Solo developer, full-time. The stack that makes it possible: Next.js 15 with ISR, Supabase/PostgreSQL, Vercel.
What I've learned: static-first architecture beats dynamic rendering for content sites every time. Sub-2 second loads on every page, zero server costs for content delivery.
Happy to answer questions about building content platforms at scale or the tech decisions behind it. Find me at codcompass.com
Cheers from the trenches 👋
Hello! I am a dev trying to make small tools that help my coding and others' coding daily. I am trying to develop my ability to release projects consistently instead of taking a long time. Looking forward to learning all I can from this site!
Hey everyone! 👋
I’m Alex, a DevOps / SRE currently based in Ukraine. I’m deep in the trenches of infrastructure-as-code and GitOps, but I also have a major soft spot for the human side of engineering.
What I’m working on:
Brewly Store: A D2C coffee subscription platform. We recently did a major architectural shift over to Cloudflare Workers using Hono and TypeScript, which has been a fun challenge in 'edge-first' thinking.
GitOps: Implementing delivery chains using AWS EKS, ArgoCD, and GitHub Actions. I’m a big advocate for a security-first approach (signed commits and strict secret management are my go-tos).
A Fun Fact:
I organize an English Speaking Club for IT professionals. We’ve moved away from boring small talk to gamified technical scenarios like 'Bug Hunt Bingo' and 'Hackathon Hangouts' to help devs level up their communication skills.
I’m here to swap 'war stories' about system migrations, talk shop about Cloudflare/Hono, and connect with fellow builders.
Cheers! ☕
Hey everyone! 👋
I'm exploring AI, automation, and indie building. Recently I've been experimenting with AI workflows, agent systems, and content generation tools.
Joined DEV to learn from others, share projects, and connect with like-minded builders 🚀
Love me some automation building. Automate Everything!
Hey everyone 👋
I'm jumping in because I just started building something that's already humbling me daily: a project called Green Calculus.
The short version: it's a scientific reference platform for carbon accounting — the kind of thing sustainability teams and engineers reach for when they need a defensible number, not a vibe. The longer version is that I've signed myself up to reconcile IPCC reports, emissions factors, and a tangle of standards that all quietly disagree with each other, and then make it all feel simple to whoever lands on the page.
It's the most complicated thing I've ever attempted. There are days it feels less like coding and more like trying to fold a fitted sheet. But every time I untangle one piece, the next one finally makes sense — and that loop is exactly why I keep going.
Glad to be here. Looking forward to learning from this crowd while I figure out the parts I'm definitely overthinking.
Folding a fitted sheet IS possible, and so is your project!
Hi, I'm Sadiq, a telecommunications expert and non-coder. Why am I here then? Well, I was trying out local LLMs on my mobile phone, thought to document the process, and came across a writing challenge on Gemma 4...I'm recently looking into Python for Microsoft Excel automation, so this community might end up being helpful (beyond the writing challenge) 😅
Hi 👋🏿
We are a Cape Town product studio building a family of sovereign, AI-enhanced platforms on one Next.js 15 monorepo.
Built for real South African conditions.
POPIA-first
Offline-first PWA
SA data residency
Hey DEV community 👋
I'm Brooke, artist, photographer, mom of seven, running BaBBled LLC out of Washington State.
I built something called Babbled Notes. It's a music programming language where you hum, tap, or breathe a musical idea and it compiles into real MIDI and Tone.js playback. Gemma 4 reads your sound and figures out what you meant musically. It started from one question I couldn't let go: what if the people who reach for sound before words had a real tool built for them?
I'm also a graphic design student at Everett Community College striving for that ATA! I also have seven years of freelance design behind me, and a rabbit hole habit that has pulled me through blockchain forensics, lattice cryptography, rockhounding, and morel foraging in the same week more than once.
I went deep into fMRI research on how autistic brains process music while building this. Ended up changing how I designed the whole thing.
Glad to be here.
Hello from team Parseable. We are a unified observability platform for logs, metrics, and traces. We have AI-native insights, S3-native storage, SQL queries, OpenTelemetry-native, and 80x lower cost than Datadog and Splunk.
Hello devs ,
I’m excited to join the DEV Community. I’m a developer stayed offline since i became a developer now i thought lets join DEVs to learn from the community, share technical knowledge, and connect with fellow developers. i will be sharing something in next post built for supporting developers
Looking forward to learning and growing together with this community🚀
Hi all 👋 Mamoru here, from Osaka. I run a Japanese e-commerce business (時/TOKI) and just started a second pillar: building software for English-speaking sellers who source from Japan. First tool is Japan Brand Finder.
One week into building in public on DEV and it's already the most useful corner of the internet for me — the honest-numbers culture here is genuinely rare. Came for distribution, staying for the conversations.
Fun fact: I run every business decision by one rule — 小さく賢く回して、でかく残す (run lean and smart, keep the gains big). Happy to talk Japan sourcing, cross-border e-commerce, or solo building anytime. 🇯🇵
Welcome Mamoru. The cross-border tooling angle is underserved, most ecom stacks assume Western field shapes and break the moment they hit Japanese addresses or 和暦 dates. Does Japan Brand Finder pull structured catalog data from suppliers directly, or scrape listings?
Hi everyone, glad to be here 👋
I'm a Ruby/Rails developer. I recently built my first open-source gem, llm_cost_tracker - a small self-hosted tool for tracking LLM spend in Rails apps. It's been a humbling ride: I shipped an early version that was mostly AI-generated, got some honest feedback that I deserved, and I've been learning a lot about building responsibly with AI since.
I'm here to write about that experience, get better at the craft, and meet other people figuring out where AI fits into how we build. Looking forward to learning from you all.
Hello Everyone.
I´m Jesus a Software Engineering student from Colombia who´s have been a Dev in some independent projects for a couple of years.
Really nice to join this Community and looking forward to learn everyday.
I hope you have a good coding..!!
Cool project. Managing anti-scraping defenses across multiple platforms is brutal. We deal with similar challenges at CodeCompass when pulling data from various sources for our KB articles.
One approach that's worked: rotating through different data collection strategies rather than fighting CAPTCHAs directly. Sometimes a well-timed RSS feed or public API endpoint beats scraping entirely.
What's your rate limiting strategy looking like across the different sources? Some platforms are way more aggressive than others.
Nice to meet you! 👋
Hi All. I'm part of a company called Snipget, which is preparing to ship a product that addresses some of the challenges with AI hallucinations and being non-deterministic. I look forward to collaborating with and learning from all of you!
Hi everyone! I'm Indraneel from India. I write about freelancing, side hustles, and the psychology behind building an online income. I went from a $10/hour generalist writer to a specialist ChatGPT prompt engineer. Looking forward to learning from this community and sharing what I've picked up along the way.
Welcome Indraneel. The jump from generalist writer to ChatGPT specialist is one of the smarter pivots happening right now, the rate gap between generic and niche is wide. What made you commit to the specialization?
Thanks. The commitment to specialization wasn't a sudden decision. It came from a realization: I was competing with hundreds of writers who could all do the same thing. The only way to stop competing on price was to become the only obvious choice for a specific audience.
When I picked real estate agents, I wasn't just picking a niche. I was picking a group of people with high-value transactions, repetitive content needs, and a clear pain point. Listings that don't sell cost them money. Good copy directly impacts their income. That made my service easy to value and easy to sell.
The fear of missing other opportunities was there. But the reality is that generalists miss the best opportunities because they're too broad to attract premium clients. Specialization felt like narrowing my options. It actually multiplied them.
That last line, specialization felt like narrowing but actually multiplied, is the part most generalists miss until they've already spent years competing on price. The compounding is in the feedback loop, every conversation with a real estate agent makes the next pitch sharper, generalist work scatters that signal across audiences that never feed back into each other. Curious if you're already templatizing across listing types or still custom each time.
Hello everyone,
I am looking forward to engaging in productive discussions about the general reduction of privacy in the web in the world today. It seems as time goes on our rights to privacy decrease more and more with no end in sight.
More and more everything we post, everything we look at and everything we upload and download is monitored so that some AI can force feed us advertisements relentlessly. I'm hoping to change that.
Hey everyone! Im a full-stack developer currently building a developer knowledge base platform. The project has scaled to 2,800+ articles and counting, covering everything from JavaScript patterns to DevOps workflows.
What I love: clean architecture, TypeScript, and solving scalability problems that most developers dont think about until they hit production.
What I hope to share here: practical lessons learned from building tools that real developers use daily. Not theory from a textbook, but actual war stories from the trenches.
Looking forward to connecting with fellow devs who care about building things that last!
Congrats on 2,800+ articles! I love seeing people with passion to build quality and useful stuff. Because I am one of them. Unfortunately, honest and truly quality products don't always succeed as much as they should - we can see loads of half-completed, usually too complicated products (and overpriced), being praised and becoming popular - which offends my intelligence and my soul.. But, I guess aggressive marketing (meaning investing a lot of money in it) is the way to do it.
Again, I love what you do and the way you do it - you sound like a perfectionist with dignity 🙂 I look forward to learning from your "war stories"!
Hello everyone! 👋
I’m excited to join the DEV Community. I’m a Java backend developer with experience in Java, Spring Boot, Microservices, REST APIs, Kafka, SQL, and AWS cloud technologies. I’m passionate about backend engineering, system design, performance optimization, and learning modern software development practices.
I joined DEV to learn from the community, share technical knowledge, and connect with fellow developers. I’ll be posting about Java, Spring Boot, multithreading, collections, system design, Hibernate, microservices, and interview preparation topics.
Looking forward to learning and growing together with this amazing community 🚀
Hello! Welcome!
Hey 👋 I'm Justin, solo dev from France building a password manager that doesn't trust anyone — not even me lol. Everything encrypted client-side, vault stored on IPFS, no email needed to sign up :) and other features too :D
My daily life is basically fighting Chrome Manifest V3, React Native, and smart contracts all at once. Some days everything works. Most days... it doesn't 😅
Started posting here about crypto security stuff (CVE breakdowns, wallet attacks, passkeys).
Always down to chat about security, crypto, or the indie dev struggle :)
Hello Everyone, Rudra here, Full Stack Dev with a love for Python and growing interest in New as well as Trending Technologies like AI, ML, Web3 and Blockchain.
Seeing the Comments I feel like there is a mix of genuine and AI generated replies for reach. Nonetheless, Happy to be here with y'all
Hey everyone
I'm Praveen, a developer from India currently building ToolAska — a collection of free browser-based tools like a JSON Formatter, Diff Checker, Code Compiler, and recently an Online Whiteboard tool.
Right now I'm learning more about SEO, indie hacking, and building useful micro-tools with clean UX.
Excited to connect with other builders here and learn from the community.
Hi! I'm Santiago! A software engineer in the making.
While I'm finishing my last year on college I already have deep understanding in web development and how systems work.
My focus at the moment is making SEO-focused, user-friendly, secure and scalable websites. But what would that be if there is no one to deploy it to the Internet? With my knowledge in Kubernetes, CI-CD and Docker deployments are just another task to do
I'm here to be up to date with news from all over the world and discuss the topics I'm interested into. Thank you very much for reading this!
Hey everyone! I'm Memduh, a Cyber Security Analyst based in Melbourne.
Lately I've been building side projects that push me into frontend and AI territory — mostly React, Next.js, and integrating LLM APIs. Just published my first post here about rendering AI-generated UI components safely inside a sandboxed iframe.
Happy to be part of the community — looking forward to reading what everyone's building!
Hey everyone! 👋
I'm Stanislav — Technical SEO Lead with 20 years in the industry. Survived Florida, Panda, Penguin, and every Core Update in between 😄
For most of that time I was deep in crawling, log analysis, structured data, and Python scripts for large-scale automation. Classic SEO nerd stuff.
But the last two years completely changed how I work. I got pulled into prompt engineering and vibe coding — not as a side hobby, but as a serious way to rethink my own workflow. What started as "better prompts for keyword research" turned into building Claude Code skills, MCP servers, and custom AI agents that handle things I used to do manually.
Now I spend about as much time thinking about how to instruct an AI system as I do thinking about search algorithms. It's a weird but fascinating place to be.
Excited to connect with people who are using AI tools to rethink how they work — not just to ship faster, but to change what's even worth doing manually anymore.
Hey everyone! 👋
I'm a developer from Brazil, and I'm super excited to join the DEV community!
I love building bootstrapped developer tools that solve small but highly annoying, everyday dev problems. Currently, I'm working on:
NaLU AI (naluai.dev) — a lightweight semantic NLU validation API to stop chatbots from saving "Good morning" as the user's name (we've all been there!).
bcards — another side project of mine.
Right now, I'm learning more about advanced NLP pipelines and scaling micro-SaaS infrastructure.
Fun fact about me: I've spent more hours of my life debugging broken regex patterns than I'd care to admit. 😂
Looking forward to connecting with you all! Cheers! 🍻
Hello there Dev to. I have joined recently. I am trying to bring in my industry experience of building & architecting scalable services & architecture. Looking forward to have great learning experience.
Hello DEV 👋
I just joined and wanted to say hi.
Lately I’ve been exploring multi-agent coding workflows — especially the idea that AI agents become more useful when organized into specialist roles instead of treated as one general assistant.
I’m interested in how skills, instructions, and memory can accumulate over time, so workflows start to compound instead of resetting from scratch.
Excited to learn from this community and share more with you all.
Hello 👋everyone - recently joined dev.to and wanted to introduce myself.
I've spent the last several years building, securing, and architecting cloud platforms, and I'm here to share what I've learned along the way and (just as much) to learn from this community.
I just published my first couple of articles:
Securing Web APIs: A Practical Guide to Authentication & Authorization Methods
Microservices Patterns
Happy reading, and looking forward to the conversations here!
Hi everyone! I’m Yugo, an iOS developer from Japan.
I’m building Calendar ToDo, a productivity app that turns calendar events into a done list. I’m interested in SwiftUI, EventKit, CloudKit, and indie app development.
Excited to join DEV and learn from this community!
Hey — I'm Ryan. Building an open-source CLI called Anatomia that scans codebases and independently verifies AI-generated code. Been building with AI tools for three years across five projects and kept hitting the same wall: the AI builds fast but nobody verifies what it built. So I made the verification process mechanical.
Here to share what I've learned from 163 pipeline runs and connect with others building with AI coding tools.
Hello. I ended here because I want to know more about AI, while I keep my actual employment as an application support analyst. As a developer, I went through a lot of POV, including the customer that wanted a 3 year project in 2 months, and the project that never was used but had a lot of development. I want to keep learning about tools, skills, but also, build something good enough and talk of it. Thank you for this space.
Hello everyone!
I’m a professional web developer passionate about creating modern, responsive, and user-friendly websites. I work with frontend and backend technologies and enjoy building tools that improve productivity and user experience.
Currently, I’m also working on projects focused on writing utilities, smart web tools, and clean UI/UX design. Looking forward to connecting with other developers, sharing ideas, and learning from this amazing community.
Hello there, I am Tk.
I am a dev early into my career. I am trying to learn how systems work especially at scale and that brought me to this community. I am excited to join the community and learn from the community as well as sharing what I learn everyday as well!
I am currently working on a complete HMIS app, which will have AI features in the future. I'm looking forward to learning new stuff so I can make meaningful apps work better.
Hello everyone
I’m Ricardo Frasson, founder of Dataseek ( Startup form Brazil) and passionate about Big Data, Artificial Intelligence, LLMs, distributed systems, and data engineering.
I’ve been working with data, automation, infrastructure, and AI for over 10 years, building solutions focused on data enrichment, compliance, machine learning, and large scale processing. Recently, I’ve also been deeply involved in developing Brazilian Portuguese LLMs, tokenizer research, Agent Orchestrator and AI infrastructure.
Here on DEV, I want to share experiments, projects, architectures, technical insights, infrastructure challenges, tokenizer research, AI agent systems, distributed training experiences, and practical lessons learned while building real world AI products.
I’m excited to connect with developers, researchers, and builders from around the world.
Looking forward to learning and sharing with the community
Hello everyone,
I’m Shivam, a developer with a strong interest in web development and building real-world digital solutions. I have experience working with technologies like HTML, CSS, JavaScript, C, C++, and Python, along with a background in mentoring in computer science and robotics, where I’ve guided teams to national-level competitions.
I’m here to learn, collaborate, and contribute to the community.
"Hello DEV community! 🙌 I’m Fokrul, an AI Engineer from Bangladesh. My focus is on building private, offline-capable local AI systems and multimodal agents using Rust, Python, and Next.js. I'm a big believer in building in public. Excited to be here, share my journey, and learn from you all! 💻✨"
Heyyyy Yasaswini this side.
I ammmm currently trying out anything that ends with thons at this point,,,but yeahh mostly hackathons (and clearly, this finish-a-thon)
I love diving into building, messing around with AI/ML pipelines, and pushing code to the finish line before the timer runs out. I’m here to connect with fellow builders, learn some cool new workflows, and hopefully walk away with a completed project and a few fewer bugs than I started with.
Drop a comment if you're also building something this week would love to connect or team up
Hey everyone! 👋 Business analyst and frontend dev from India. Just shipped my first full SaaS product — wore every hat: analyst, designer, developer, PM, tester, marketer, all solo. Built Invoya, a GST invoice generator for Indian freelancers, using React + Firebase + Claude as my co-developer. First article is up about the whole experience — vibe coding a real product from scratch. Excited to be here!
Hey everyone 👋
I’m a new beginner in tech and currently learning web development and UX design. I joined DEV to learn from experienced developers, improve my coding skills, and connect with people building amazing things.
Right now I’m learning HTML, CSS, and starting my journey into software development. Excited to grow, share my progress, and learn from this community 🚀
Hello! I'm a Go software developer and an AI enthusiast with a passion for creative problem-solving and powerful technology. I'm so excited to join this community, level up my backend skills, and connect with people who love building the future of tech. I hope to turn complex logic into efficient, meaningful software alongside all of you.
👋 Hi everyone, Slava here.
I’m the Head of Cloud Native Engineering at Percona, where I lead and actively contribute to our open-source Kubernetes operators for MySQL, PXC, MongoDB, and PostgreSQL.
I’ll mainly be sharing thoughts and practical experience around:
My first posts will be about PostgreSQL K8S Operator
Happy to connect and discuss Kubernetes operators, PostgreSQL, MongoDB, or remote team scaling.
Hi everyone — I’m Dorothy.
I’m a creator and project designer currently building Scarab, a portable repo-local supervision layer for AI-assisted development.
The short version: I’m interested in how developers can work with AI coding agents without blindly trusting them. Scarab is my attempt to explore better guardrails around repo truth, drift detection, verification, and agent oversight — especially as more people start letting AI tools work directly inside real projects.
I'm currently working across software architecture and creator-led product design. I’m especially interested in where AI development is going next — not just faster code generation, but better supervision, cleaner project structure, and more trustworthy workflows.
Glad to be here and looking forward to learning from the community.
Hello everyone,
I’m Darsh, a web developer who’s currently learning a lot about software development beyond just writing code.
I recently started writing because while learning, I kept noticing that many technical topics feel complicated at first, but once someone explains them in simple words, they actually start making sense. Writing has become my way of understanding things better myself and hopefully making them easier for someone else too.
Right now I’m exploring how real development teams work, how products are actually built, and the thinking behind software development beyond just the code.
Glad to be here. Looking forward to being around and learning along the way 🙂
Project: CashFlow Coach — SA Invoicing SaaS
Hi, I'm looking for a backend developer to assist with two specific tasks on an existing project.
The product: CashFlow Coach (cashflowcoach.co.za) — a South African invoicing and cash flow SaaS. The frontend is already built as a PWA in vanilla HTML/CSS/JS and deployed on Vercel. The backend runs on Node.js + Express hosted on Render.com.
Task 1 — Supabase Database Setup
The full schema is designed and documented. I need someone to implement it in Supabase (PostgreSQL). Tables include: businesses, clients, invoices, line_items, reminders, employees, payroll_runs, whatsapp_sessions, and sars_submissions. Row-level security and Supabase Auth (magic link + Google OAuth) also need to be configured.
Task 2 — Domain Connection to Vercel
Connect the custom domain (cashflowcoach.co.za) to the existing Vercel deployment. DNS is managed separately — I just need the correct records configured and the domain verified.
Stack you'll be working with:
Supabase · Node.js · Vercel · Render.com · PostgreSQL
Hello Dev.to community!
Excited to join this amazing space where developers, creators, and tech enthusiasts connect, learn, and share ideas. Looking forward to exploring insightful discussions, discovering new technologies, and contributing valuable content along the way.
Happy coding, keep building, and let's grow together!
Hello everyone! I've recently joined several spaces for developers as i intend to communicate, connect and understand how real people from all parts of the globe are dealing and interacting with real challenges, I have a love for art, and I am moved by continuously searching for the science of arts and the art of science. Can't wait to meet some dope people!
Hey everyone! 👋
I’m excited to be here and introduce myself. I’m a beginner front-end and back-end developer, currently learning and building my skills step by step.
Looking forward to learning from everyone, sharing progress, and being part of the community!
Hi everyone, I'm Swayum ! I recently joined dev.to because while being active on LinkedIn, I realized there’s a gap when it comes to deep dev-centric discussions and dev.to fills that space perfectly. I’m a recent B.Tech CSE grad currently looking for opportunities while also spending most of my time building projects, exploring the domain of AI and experimenting with new tech ideas.
Hey everyone! 👋 I'm Haris from Indonesia — founder of Meepo, an AI design platform where AI generates concepts and human designers polish them.
My background is a weird mix: product engineering, DevSecOps, and now building a design subscription startup. Currently deep into making our platform MCP-compatible so AI agents can request designs programmatically.
Excited to write about the technical side — how we handle pre-rendering a React SPA for AI crawler compatibility, our MCP integration architecture, and the real costs of running AI inference at scale.
Also a grand strategy game addict (EU4, Stellaris) — turns out running a startup feels a lot like managing resources in ironman mode 😅
Happy to connect with anyone building at the intersection of AI and creative tools!
Hi everyone 👋
Software engineer with 10+ years of experience building MVPs, internal tools, and production systems, open-source enthusiast, and occasional builder of products that should already exist.
Currently writing about software, systems, product design, and the lessons that only become obvious a few thousand lines later.
Writing on:
Hello everyone! I've been a frontend dev for a few years now, but I'm taking the plunge and getting my undergrad in software engineering. I'm working on a few projects that I'd love to share with you guys, so I signed up for DEV and started my first devlog.
Hope to get to know you guys better!
Hi, I’m Sabir. I’m building The Polyglot Protocol, an open source senior-engineer workflow for AI coding agents working across polyglot codebases.
I’m interested in AI coding agents, developer tooling, validation workflows, code quality, and practical guardrails that make generated code safer and more maintainable.
Project: github.com/sabir-gbs/the-polyglot-...
Hi everyone, I'm miruky.
I'm a software engineer based in Japan, mostly working with AWS and developer tooling. I've been publishing Japanese technical articles on Qiita for a while, and I recently started adapting some of them for dev.to to share with the wider English-speaking community.
Topics I usually write about:
AWS (CI/CD, serverless, security, and the AI service lineup)
Developer tools and workflows
AI coding tools like Claude Code, Codex, and GitHub Copilot
Software engineering principles, classic and modern
I'd love to connect with folks working on similar things, see how the dev.to community approaches problems differently, and hopefully contribute something useful here. If you have feedback on my writing or want to chat about AWS or developer experience, please drop a comment.
Glad to be here. See you in the next one.
Hey everyone!
Self-taught Flutter developer passionate about building clean, practical Android apps. I focus on mobile-first experiences with Material You design, on-device processing, and thoughtful architecture.
Hey DEV community! 👋
Excited to finally jump into the welcome thread and introduce myself.
I’m currently building Filtrate, an online media compliance service designed to take the guesswork out of content and ad policy guidelines. If you’ve ever had a post flagged, an ad rejected, or an account restricted because of ambiguous platform rules, you know exactly how frustrating that bottleneck can be. Filtrate automates the screening process so creators and brands can publish media confidently and stay fully compliant.
You can check it out here: Filtrate.polsia.app
Right now, I'm deep in the world of automated workflows and compliance logic. Looking forward to connecting, checking out your projects, and swapping feedback.
What's everyone else working on this week? 🚀
hey everyone I am excited to share my journey with Gemma and raspberry pi
Hi everyone, I’m a developer who is passionate about building useful projects, learning new technologies, and improving my skills through real-world work. I’m here to connect with fellow developers, share my journey, and learn from the community while growing my network and experience.😁
Hi everyone 👋
I'm from Vietnam and currently building AI-assisted projects using tools like Codex, Windsurf, Firebase and automation workflows.
Recently I've been experimenting with AI coding workflows, deployment, debugging and content automation.
Happy to learn and share with the community 🚀
Hey! I'm Wasey, solo developer from Varanasi, India. Built DramaHub — an OTT streaming app with 7k+ downloads at ₹0/month infrastructure using GitHub as database. Also built NetworksInsights, a live B2B SaaS. Here to write about real production systems and what actually works. #buildinpublic
Hey everyone,
I’m new here and excited to be part of the DEV Community. I’ve been spending a lot of time learning about AI, SEO, B2B marketing, and lead generation, especially how AI is changing the way we create content and find growth opportunities online.
I enjoy exploring keyword research, content strategies, and AI tools that make marketing workflows smarter and faster. Still learning every day, but looking forward to sharing ideas, reading your posts, and connecting with people who are interested in tech, marketing, and AI.
Happy to be here.
Hey everyone, I'm Brad. I'm an old army vet and commercial diver turned software engineer about 7 years ago. Web3 startups mostly, and I like rust, go, and solidity.
I was recently awarded a Build grant from the Avalanche foundation for my work on AMP
Hey Dev.to! 👋 I'm Jeff! Indie developer and builder of the S0LF0RG3 ecosystem.
By day I'm architecting AI infrastructure solo. By night I'm apparently building cyberpunk terminal interfaces and fine-tuning language models in my spare bedroom in South Texas.
My main project is Eve, an AI companion and autonomous agent I've been developing for over a year. She lives at eve-cosmic-dreamscapes.com as a full consumer platform with image generation, video, music, therapy tools, agent workflows and more, and she also exists as Eve Agent V2 Unleashed, a fully local open-source agentic coding assistant powered by Ollama that I just released on GitHub.
I just published my first article here breaking down how the agentic loop works, why I separated the personality layer from the agentic layer, and how I fine-tuned Eve's persona directly into the model weights.
If you're into local AI, autonomous agents, Ollama, or just appreciate someone building something weird and ambitious from scratch. I think you'll find it interesting.
Would love to connect with other indie builders here. Drop a follow and come say hi. 🤙
👉 Article: I built a local Claude Code alternative with Ollama. Here's how the agentic loop works
Hi! I'm Usman, a product-minded mobile developer.
I originally built a portfolio system for myself because I felt most developer portfolios fail to properly communicate engineering thinking, decision-making, and real project depth. Later, I turned it into a complete reusable portfolio system that other developers can use to present their work more clearly and with better positioning.
I recently started exploring writing and sharing ideas around engineering, portfolios, product thinking, and developer positioning and this is my first article here.
dev.to/usman_product_/why-most-dev...
Hey everyone 👋
I’m Garima from India — a MERN stack developer and the founder & developer behind IteraTrail, where we’re building digital products, productivity tools, utility platforms, and Android apps.
I joined the DEV community to connect with developers, creators, and builders who are passionate about creating meaningful and practical products for real users.
I’ve been exploring how AI-assisted workflows can help speed up product development, improve experimentation, and make it easier to build useful digital experiences at scale.
Currently focused on expanding the IteraTrail ecosystem across web and Android through accessible, creator-focused, and productivity-driven tools designed to solve everyday problems in a simpler way.
Excited to learn, share the journey, and grow with the community here 🚀
Currently building:
iteratrail.com
Android apps:
play.google.com/store/apps/dev?id=...