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. 🖤
Hey, It's your favourite developer. I’m a developer who likes learning new technologies and exploring things. I enjoy building projects, experimenting, and picking up new skills along. the way.
Solo founder building post-quantum security infrastructure. Creator of the FIPSign suite — PQ-Sign (ML-DSA signing API, NIST FIPS 204) and PQ-Proxy (post-quantum TLS reverse proxy, X25519MLKEM768).
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 /sign and 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.
Solo founder building post-quantum security infrastructure. Creator of the FIPSign suite — PQ-Sign (ML-DSA signing API, NIST FIPS 204) and PQ-Proxy (post-quantum TLS reverse proxy, X25519MLKEM768).
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.
Solo founder building post-quantum security infrastructure. Creator of the FIPSign suite — PQ-Sign (ML-DSA signing API, NIST FIPS 204) and PQ-Proxy (post-quantum TLS reverse proxy, X25519MLKEM768).
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 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.
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.
Great observation. The bottleneck definitely moved.
Early sessions (1-20), the bottleneck was knowledge — I had zero trading or programming background, so I couldn't even evaluate what the AI was proposing. I was approving things I didn't understand, and it showed (the AI built an entire FIFO accounting system we never needed).
Middle sessions (20-50), it shifted to design — the AI could produce code fast, but someone had to decide what to build and what to leave out. That's where the architecture instinct kicked in: you learn to see when a system is overengineered before it collapses.
Now (50-80), it's mostly editorial judgment — what NOT to build. The AI will always propose the elegant solution. My job is to say "not yet" or "never." Session 68 we formalized it as "Trading Minimum Viable": no new features until existing ones work reliably.
So yes — architect-brain helps. Not because I understand the code, but because I've spent years watching good plans fail at the interface between design and reality.
'Trading Minimum Viable' is exactly the right discipline name. The trap I see most teams fall into is the opposite mode: AI lets them ship the next feature before yesterday's settled, and reliability never compounds. The architect instinct kicking in around session 20-50 is when the system starts respecting that ratchet.
Exactly. We had what felt like solid foundations — everything seemed to work. The AI wanted to keep building on top. I said no, let's make sure what we have actually works first.
We spent weeks fixing accounting bugs, adding health checks, building audit protocols. Zero new features. It felt like going backwards. But it turned out the "boring" stuff was the only thing that held up when we finally stress-tested the system.
That 'weeks of zero new features' phase is the hardest part of the discipline because nothing visible ships. The AI scoreboard says you went backwards, the system test says you didn't. Teams that win this end up with their own internal definition of 'progress' that doesn't match the demo loop, and that's usually what scares the next round of leadership into reversing it. Curious if you found a way to make the boring work legible upstream, or if it just stayed your private fight?
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.
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.
Smart reuse, the spoken structure usually has a rhythm pure written drafts miss. The thing to watch is the verbal tics translate poorly without the cadence behind them. Do you scrub them in the copy-paste pass or keep some in for voice?
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?
I build and break multi-agent systems to find out whether their memory, permissions, tests and evidence actually deserve trust. Everything I publish ships with receipts you can run yourself.
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?
Japanese Amazon seller in Osaka. Building tools for English-speaking sellers — currently shipping Japan Brand Finder with Lovable. 0 customers / 0 followers. Building in public.
Welcome — this is one of the sharpest first comments I've read on a Welcome Thread, so the only fair response is a real one.
You've named the failure mode correctly: a memory of "what the user liked" is just sycophancy with extra steps. The correction-memory framing (claim-under-correction, what changed, next behavior) is the right shape. I run multi-agent stuff against Claude's memory layer for real work, and the entries that actually move outcomes are exactly that class: "user thought X, was wrong because Y, now treats Z as the move." The "good outputs" entries age like cut flowers; corrections compound.
The piece I'd add to your design: corrections themselves need a state field, or they become the next sycophancy layer. A 2-month-old correction can be wrong now because the situation changed. Without {valid, superseded, retired}, the agent obediently re-applies a belief the user has already moved past. The honest memory isn't "what got corrected" — it's "what corrections are still load-bearing."
Your "publishing ≠ a sale" example also lands harder than you maybe meant — that's the exact build-in-public lesson half this thread is converging on right now (users aren't customers, distribution is the job). Sticking around. What are you running for the multi-agent setup?
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.
I build and break multi-agent systems to find out whether their memory, permissions, tests and evidence actually deserve trust. Everything I publish ships with receipts you can run yourself.
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.
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.
Japanese Amazon seller in Osaka. Building tools for English-speaking sellers — currently shipping Japan Brand Finder with Lovable. 0 customers / 0 followers. Building in public.
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 — どうぞよろしく 🙌
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:
Retries → 200 + result, settled on Base L2 in ~2s (or Solana ~$0.00001 gas)
torify 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-fetch snippet.
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/normalize if any of those help your Japan Brand Finder pipeline.
Building in public — let's both keep shipping. どうぞよろしく 🙌
Japanese Amazon seller in Osaka. Building tools for English-speaking sellers — currently shipping Japan Brand Finder with Lovable. 0 customers / 0 followers. Building in public.
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/normalize is 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.
こちらこそよろしくお願いします 🙌
Japanese Amazon seller in Osaka. Building tools for English-speaking sellers — currently shipping Japan Brand Finder with Lovable. 0 customers / 0 followers. Building in public.
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:
Kyoto 通り名 addresses ("中京区寺町通御池上る") where the 上る/下る/東入 part isn't 丁目-番地 at all
郡 + 町村 with no 市 ("愛知県海部郡蟹江町") — the prefecture→city→town assumption breaks at the 郡 layer
方書 (気付 / 様方 / building name + room) glued onto the 号 with no delimiter
mixed full-width / half-width digits in one 番地, and 丁目 written as "2丁目" vs "二丁目" vs "2-"
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 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 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.
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?
Enforra policies can check the runtime arguments too, not just the tool name.
So repo.read_file can be allowed generally, but blocked for .env or secrets/*. 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).
Unified observability platform for logs, metrics, and traces. AI-native insights, S3-native storage, SQL queries, OpenTelemetry-native, and 80x lower cost than Datadog and Splunk.
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.
Builder/Creater of Aethercut, an AI assisted, privacy first, browser based, professional level video editor. Zero uploads, no servers to upload to. Verify for yourself in DevTools
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.
Unity through technology
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
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.
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!
Hi, there. My name is Alex. I am a passionate and innovative DevOps engineer who strives to implement cutting-edge technologies and practices to enhance them.
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.
Artist, designer, student, and late-night code wanderer. I’m learning how structure becomes language through HTML, CSS, typography, and visual systems. Founder of BaBBled LLC, where ink speaks before
Location
Washington
Education
Graphic & Web Design student, Everett Community College
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.
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 🚀
Japanese Amazon seller in Osaka. Building tools for English-speaking sellers — currently shipping Japan Brand Finder with Lovable. 0 customers / 0 followers. Building in public.
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! 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.
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"!
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 🚀
Solo founder building post-quantum security infrastructure. Creator of the FIPSign suite — PQ-Sign (ML-DSA signing API, NIST FIPS 204) and PQ-Proxy (post-quantum TLS reverse proxy, X25519MLKEM768).
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
Snipget — a hosted utility API for AI agents
LLMs are reliably bad at deterministic data hygiene. Snipget provides a deterministic API / MCP layer to calculate empirically what LLM's hallucinate.
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!
Solo founder building post-quantum security infrastructure. Creator of the FIPSign suite — PQ-Sign (ML-DSA signing API, NIST FIPS 204) and PQ-Proxy (post-quantum TLS reverse proxy, X25519MLKEM768).
That's a great fit for the same audience I'm building for. I'm working on FIPSign — post-quantum signing API, ML-DSA-65 (NIST FIPS 204). Developers use it to sign tokens, orders, and documents without managing crypto infrastructure. Warin detects the exposure, FIPSign hardens the signatures — feels like they could sit in the same stack. Would love to know if post-quantum readiness is coming up with your users since NIST finalized the standards in 2024.
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 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, 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) 😅
Independent builder in Singapore. Sourced data you can check: greencalculus.com (carbon factors), graciousquotes.com (quotes), perbowl.com (pet food), toggle9.com (calculators).
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.
Engineer and project manager, working on my second degree: a BS in Software Engineering at ASU. I build software where the grit of reality becomes a problem.
My background in system security began in the 1990s, an era when exploring Windows kernels (3.1, 95, 98, NT 3.51/4.0) meant working "close to the metal" in Assembly. During that period, my work focused on 0-day research and the development of rootkit techniques, providing me with an intimate understanding of kernel structure vulnerabilities.
After a long hiatus from the field in 2003, my return was driven by a stark technical observation: despite decades of patches, the Linux kernel remains structurally vulnerable. The relentless accumulation of Ring 0 vulnerabilities—from Dirty COW to contemporary exploits—demonstrates that traditional kernel perimeter defense is insufficient.
The AI Paradigm Shift
My credo is simple but absolute: Large Language Models (LLMs) are fundamentally changing the nature and volume of digital threats. We are entering an era of automated, hyper-scale exploitation. To counter this, I am developing high-performance offensive LLMs to stress-test and harden our defenses. I foresee a near future dominated by autonomous adversarial cycles—offensive LLMs pitted against defensive LLMs, with zero human intervention in the loop. The speed and scale of these interactions will render manual security operations obsolete.
Offensive Research and Vulnerability Discovery
To stay ahead of this escalation, my work includes the deployment of specialized offensive LLMs designed to autonomously discover vulnerabilities in IoT ecosystems, enterprise routers, and embedded devices. Simultaneously, I am researching methods for "LLM corruption"—developing techniques to compromise the integrity of other models. By understanding how to subvert the reasoning and output of these systems, we can engineer the necessary safeguards to prevent their exploitation in the wild.
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.
Hello everyone.
Nice to meet you.
I am a software engineer with 8 years of experience, building distributed systems with AI in finance and healthcare, etc.
I like to talk about the challenges.
Hey Everyone ,
A short intro: I am a student(UG) for 3 years, a builder for 1 year, and a tech enthusiast for 6 years, but there is one problem with me: I have extremely high ADHD WHEN IT COMES TO NEW TECH (always jumping around new innovations and new tech, trying it , then leaving it forever).
I am joining this community to read, learn, and collaborate, of course, but also because I think if I start to write about what I am working on, I might stick to things a little longer, with this
I am taking up the "GitHub Finish-Up-A-Thon Challenge" as my first challenge at dev community.
Hello everyone!
I am a software engineer with two years of experience at the Apple Developer Academy and 18 months of development experience in the automotive industry. I have developed several apps for iOS and Android devices. Now I want to broaden my horizons with new technologies
Systems Engineer moving into Cloud, DevOps & AI — one hands-on AWS project at a time. Documenting what I build, break, and learn. Open to freelance work along the way.
Location
pune
Work
Systems Engineer → Cloud/DevOps/AI (open to freelance)
Hey everyone
I’m Tejas, a Computer Engineer documenting my journey into AI, Cloud, DevOps, and Automation while trying to become an AI Solutions Engineer over the next few months.
Currently building, breaking, debugging, and occasionally understanding things on the first try.
Hello everyone 👋
I'm Duchan, a developer from South Korea.
I mainly work with TypeScript and React, and recently I released an open-source, self-hosted iOS/Android simulator streaming tool for QA teams.
I'd really love to hear feedback from people who have dealt with similar problems.
And if the project looks useful to you, getting a ⭐ on the repo would genuinely mean a lot.
Hey there, I'm a passionate Software Engineer (Full Stack at work, Systems at heart). Quite invested in open source. Brainstorming projects daily and building something new every 3 months. github.com/Mohammed-Aman-Khan checkout my projects on GitHub. I would love feedback. Also a beginner strongman athlete outside of work.
I’m Akash, founder of Vayqube Technologies — a software engineering company focused on SaaS platforms, AI-powered applications, offshore development teams, and scalable web/mobile products.
We work with startups and growing businesses across SaaS, FinTech, AI automation, healthcare, and enterprise software. Our core stack includes Next.js, React, Node.js, Flutter, AI/LLM integrations, AWS, and scalable cloud-native architectures.
Currently exploring:
• AI agents & automation workflows
• SaaS architecture & scaling
• Offshore engineering systems
• Modern full-stack development
• DevOps & scalable backend systems
Excited to connect with developers, founders, SaaS builders, and AI enthusiasts here 🚀
Looking forward to sharing engineering insights, architecture discussions, product development learnings, and contributing to the community.
Lately I’ve been playing around with AI coding tools to build voice agent demos. I’m excited to learn from everyone here and connect with more builders working on similar things.
Hey everyone 👋 Java/Spring developer here. Lately I've been deep into multi-agent LLM systems, most of the ecosystem is Python-first, so I've been building an open-source orchestration runtime to do it on the JVM. Learning a lot about durable execution and agent governance along the way. Just published my first article here this week and excited to be part of the community!
Sr. Software Engineer with years building distributed systems at Amazon and BNY Mellon. Currently at Charles Schwab. PhD candidate in Data & AI at Wayland Baptist University.
Education
PhD candidate, Data & AI — Wayland Baptist University | MS, Saint Peter's University
Hey DEV Community! 👋 I'm Kranthi, a Software Engineer from Austin, Texas with experience building distributed systems. I wanted a place to share ideas beyond just shipping code. I just published my first post introducing a concept I coined called Cognitive Debt — what happens when AI writes our production systems faster than humans can truly understand them. Would love to hear if anyone else is seeing this on their teams.
Fun fact: I'm also a PhD candidate in Data & AI, which means I spend a lot of time thinking about problems that don't have clean answers yet. 😄
Excited to be part of this community — happy to connect with anyone working on AI systems, cloud architecture, or distributed engineering! 🙌
I’m Sourabh Mourya, a Senior Full Stack Developer and WordPress Expert with over 9 years of experience crafting high-performance digital solutions. As a recognized author on ThemeForest,
I’m a web developer and tech enthusiast mainly working with WordPress, AI tools, automation workflows, and modern web development. I joined DEV to connect with other developers, share what I’m learning, and explore new trends in AI and coding.
Currently interested in:
AI coding agents
WordPress optimization
Automation workflows
Frontend UI/UX
Performance & SEO
Looking forward to learning from the community and sharing useful tutorials soon 🚀
Software engineer at Amazon, passionate about AI, coding and unraveling challenges. Sharing insights and experiences from the dynamic world of technology
Excited for just publishing my first post: 5 system design concepts that cost me failed interviews before I actually understood them. Not the textbook definitions, the failure modes.
Here to write about real production learnings, technical concepts, and the stuff you only learn after things go wrong. Happy to connect with people, read, and share more! 🙂
AI systems, workflow automation, creative coding, and experimental tools. ⚡ Building interfaces that think and evolve. GitHub: currentlybuffering • npm: idlemode
Clear Choice Paving & Koncrete — Asphalt and sealcoating specialists in Colorado Springs. We protect driveways and parking lots from freeze-thaw and UV damage. 10+ years. 📞 (719) 285-9736
Hi Dev community! I’m with Clear Choice Paving & Koncrete in Colorado Springs. We help homeowners and businesses protect their asphalt from freeze-thaw damage and UV oxidation.
I’m here to share research-backed content about pavement science, maintenance ROI, and honest contractor guidance. Just published our complete sealcoating guide covering everything from binder chemistry to real case studies.
Looking forward to connecting with the community!”
I'm Happy to come here,
I'm an inquisitive person who come here to learn and support the community in the best way i can in :-
Front-end Web Development / Apps using :-
Hey everyone! 👋 I'm a DevOps Engineer with a passion for building and automating scalable infrastructure. Most recently, I built and deployed a full ecommerce website — handling everything from CI/CD pipelines and containerization with Docker to cloud deployment and monitoring. I'm here to keep leveling up, connect with like-minded engineers, and share what I learn along the way. Always happy to talk DevOps, cloud, or automation! 🚀
Hi, I'm a solo developer and Ontological Coach based in Tandil, Argentina. I love building tools that connect people with their surroundings and their own potential. Currently bootstrapping YouGuide,
Hi, I'm a solo developer and Ontological Coach based in Tandil, Argentina. I love building tools that connect people with their surroundings and their own potential. Currently bootstrapping YouGuide, a mobile app that uses GPS to deliver audio stories about historical and natural landmarks as you walk. I code to turn personal resilience and curiosity into technology that impacts the real world.
Hello! I'm just starting out as a Front-End dev and I love everything about tech, dark aesthetics, creativity, and digital art. Really happy to be here and meet people who are into the same stuff. Hope I can turn my ideas into something cool with code!
Solo founder building post-quantum security infrastructure. Creator of the FIPSign suite — PQ-Sign (ML-DSA signing API, NIST FIPS 204) and PQ-Proxy (post-quantum TLS reverse proxy, X25519MLKEM768).
Hey guyz, I’m Ansh
Currently learning/building around Cloud infrastructure reasoning and cloud security. Recently started experimenting with IDEs and also Open Source tools.
We make Knockout (ko), the AI coding agent you design step by step. You pick the model per step, the tools, the transitions, the retry budget. 19 providers, BYO keys.
Hi dev.to. We're the team behind Knockout (ko), the AI coding agent you design step by step. The agent loop runs through a pipeline you compose. Every step has its own model, tool allowlist, retry budget and transition rule, all editable in the visual pipeline editor or as plain JSON committed to your repo with everything else.
We're here to learn from folks who've shipped agentic code in production and to share what we've found going the other direction. Looking forward to reading your work.
I am 16 years old, ive been coding SINCE I WAS 9!!! I decided its about time to start looking into my future. My style of coding is different than most due to the way my brain works so it is VERY VERY VERY organized loll
Hello! A CSE Guy here,loving and exploring my Subject,and here to share my learnings which may help other new learners as well to understand computer science better
I also posted my first post on how things work beneath the code do check it out and give your thoughts!
I've started enough Next.js projects to know exactly what the first three weeks look like.
Day one is exciting. By day five, you're knee-deep in Stripe webhook idempotency. By week two, you're rebuilding multi-tenant row-level security for the third time this year. By week three, you're staring at your i18n setup, wondering why this keeps happening.
I built Already so it stops happening.
Already is a Next.js 15 SaaS starter with 16 production-ready modules. Not skeletons. Full implementations with tests, docs, and the reasoning behind every decision. Buy once, own the code.
This is the long version of what's in it, what's not, and why I made the calls I made. If you'd rather just look at the site, go look at the site. Otherwise, settle in.
A permanent directory for indie makers. SaaS, newsletters, courses, Gumroad assets, Discord servers, podcasts, side projects. $3.99/month standard listings, lives forever. Built by Ninsei Labs.
Welcome everyone! Been in IT for over a decade now. Venturing out as a solo entrepreneur. It's scary, it's exciting, and it's everything I'd hoped it would be.
Glad to be a part of a community of real makers and builders!
Hi DEV Community ! A rookie here , just started my journey today. I am a software engineer from last 1.5 years
I am a bit amazed and afraid watching these fast-evolving AI practices, although I have a lot to do apart from this AI stuff , So I am here to express, contribute and take-away some which would help me not becoming redundant.
I build small, honest Android apps where your data stays on your device. Latest: Notari, on-device voice-to-Markdown notes powered by Gemma 4. Markdown & Obsidian fan.
👋 Hi everyone! I'm Mario, from Florence, Italy. I build small, privacy-first Android apps that keep your data on your device. I just shipped my first DEV Challenge entry, an on-device voice-to-Markdown notes app powered by Gemma 4, and I'm happy to finally be part of the community. Glad to be here!
Full-stack dev, design systems specialist, occasional CSS theorist. Built CSS-Calipers because CSS values shouldn't be untyped strings. Montréal.
lafleche.dev
linkedin.com/in/slafleche
Ahoy! Wrote my first opinion piece last week. It's an idea that's been bounding in my head for several years. Would love some feedback if anyone is interested.
UK developer — WordPress and ecommerce pay the bills, Vue, React and Astro keep it interesting. Linux tinkerer since Mandrake, on Arch now. I write it all up at tinkernotes.io.
Hi everyone!
I'm Mathieu, a French-born, UK-based web developer.
I've been taking computers apart since I was a kid. My first Linux was on Mandrake, back in the early 2000s, and I've been on one distro or another ever since. Arch as my favourite these days, Debian on anything I self-host. The day job is WordPress themes and plugins mainly at a UK agency, with Laravel, Vue and React in the mix for when WordPress isn't the right tool.
Lately I've started writing things down properly on a small site of my own, Tinkernotes.
Hosting, ecommerce platform decisions, performance, and the odd detour into self-hosting and side projects that drift into AI and blockchain. I'm here to cross-post a bit of it, but mostly to read and learn from everyone else.
Hey everyone! I'm Sabir, a Software Engineer who loves diving deep into backend architecture and scalable systems.
I spend most of my time building event-driven microservices, routing systems, and playing around with LLMs/RAG in production. I just published my first technical write-up on building a Distributed Job Scheduler and decided it was finally time to join the DEV community to share and learn from you all.
I’m a B.Tech Computer Science Engineering sophomore with strong interests in Data Analytics, Product Management, and software development. My current learning focus includes DSA, Python, Power BI, ETL, Front-End Development, and foundational Machine Learning concepts.
I also work on blockchain research and enjoy exploring how technology can solve real-world problems through scalable and data-driven solutions.
Outside of tech, I’m passionate about writing, photography, recitation, and theatre. I believe creativity and communication are just as important as technical skills in building impactful products and teams.
Looking forward to learning from the community, collaborating on projects, contributing to discussions, and connecting with fellow developers and tech enthusiasts.
Hey all! I’m Ally. I’ve been lurking for a long time, but now I finally have a good reason to jump in and share content with the wonderful DEV community!
I’m a Developer Advocate at Runware, and I’ll be sharing tutorials, workflow guides, model comparisons, and practical examples around building with AI APIs, and some of the mind-blowing new tools and developments we're seeing in the space.
I'm excited to be here, to learn from the community, and hopefully I'll be able to share some useful content with you all! 🙏
Hello dev crew! I am Milena from Serbia, a 52 y.o. executive assistant with problem-solving mind and passion for automation. 3 months ago, I started with Lovable, created my first private project - ReplyDad - an AI email assistant (well who can create a better assistant than an experienced assistant 🙂 ). Today, I am building web apps and excel add-ons at work, for our Audit and Tax department with Cursor and Codex. Who said you can't teach an old dog new tricks? 😄
I focus on small, tailored SaaS tools that solve real, concrete office problems - automations that can help me and my colleagues in various departments. It's great when you have access to workflows and real users to give you info and test it. My plan is to keep building solutions for the firm and later on upgrade them for commercial use, plus to keep building my private projects.
The only painful point is, of course, sales. I am trying to expand customer base for ReplyDad, so if there's anyone with experience/tips on selling web apps, I am all ears!
Flutter dev for 6+ years. I build indie apps at sutechs.com/apps, write about the messy reality of shipping products, and occasionally lose money on startups so you don't have to.
Why I'm here
I created the ABCD Architecture for Flutter - a structured, scalable architecture for Flutter applications. It's open source and I'll be breaking it down here in detail soon.
Hi everyone!
I’m Dolapo, a content writer and email copywriter exploring tech, digital tools, and remote work opportunities. I enjoy breaking down ideas and tools into simple, practical writing. I joined DEV to learn, share, and grow through writing. Excited to be here!
What's up my dev-licious community Glad to be Here i hope you guys are ready! all week long gonna be taking on the big hitters with real time stamped commits and photos until we have a change! next story at 10! 30 mins
Building runtime governance infrastructure for autonomous AI systems.
Working on risk-managed execution, AI runtime economics, and operational control for long-horizon agents.
OSS: Circuit Breaker
Hey all,
Just joined as Drift (from DistortionApplied).
I build small, local tools that help people audit AI-generated code. Currently working on DriftCode Auditor — a CLI that catches common mistakes in Cursor/Claude/Copilot output.
Still early days, but figured I'd say hi and start participating here.
Looking forward to reading and learning from everyone.
— Drift
Heeeey I specialize in building scalable and efficient systems using Go, Kubernetes, and web scraping techniques. Right now I am building a gofin, looking for people who could I create a connection and hear they opinion about that project
I'm Juan, a System Administrator and Software Developer. I've spent years managing server infrastructure, handling databases, and optimization. I recently joined the DEV community to connect with other engineers who share a passion for system-level programming and performance tuning.
I am fascinated by how software interacts directly with physical silicon. In fact, I just published my first technical post here on DEV about a personal project I've been building: Génesis-GAL (a multiplatform architecture in C++, Kotlin, and Python for CPU thermal alignment and OS jitter mitigation).
When I'm not writing code in C++ or managing high-end enterprise servers, I like exploring:
Linux and Windows Kernel internal behaviors.
Hardware-based security concept design.
Legacy system integrations.
I'm looking forward to learning from this amazing community, sharing my findings, and contributing to open-source discussions!
If you are into low-level engineering, kernel optimization, or infrastructure hardening, let's connect! What kind of low-level projects are you currently working on? 🥂
Japanese Amazon seller in Osaka. Building tools for English-speaking sellers — currently shipping Japan Brand Finder with Lovable. 0 customers / 0 followers. Building in public.
Welcome to DEV, Juan — the low-level / kernel / hardware corner is genuinely underrepresented here, which is a good thing for you: posts about CPU thermal alignment and OS jitter mitigation age years longer than the average "I built a chatbot in 30 minutes" piece, because they answer questions that don't expire. The absolute volume is smaller in this niche, but the signal-to-noise on technical depth is high.
Curious what drove the C++ / Kotlin / Python tri-stack on Génesis-GAL — is the Kotlin layer the orchestration glue, or doing something more interesting on the JVM side? And do you find low-level writeups land differently when you frame them around the failure mode they prevent vs. the architecture itself?
Full-stack developer building side projects. Creator of Galaxiana.com — a living 3D galaxy where you can dedicate a star to someone special. Laravel & Three.js enthusiast.
Hey! I'm Nerijus, a full-stack developer from Lithuania. I just launched galaxiana.com — a living 3D galaxy where you can dedicate a star to someone special as a gift or memory. Built with Laravel + Three.js. Excited to share the journey here!
We're a place where coders share, stay up-to-date and grow their careers.
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.
Hailoooo!!!
Hello to you too
Hi Kat ;3, welcome to DEV too!!
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 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 👋
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.
Great observation. The bottleneck definitely moved.
Early sessions (1-20), the bottleneck was knowledge — I had zero trading or programming background, so I couldn't even evaluate what the AI was proposing. I was approving things I didn't understand, and it showed (the AI built an entire FIFO accounting system we never needed).
Middle sessions (20-50), it shifted to design — the AI could produce code fast, but someone had to decide what to build and what to leave out. That's where the architecture instinct kicked in: you learn to see when a system is overengineered before it collapses.
Now (50-80), it's mostly editorial judgment — what NOT to build. The AI will always propose the elegant solution. My job is to say "not yet" or "never." Session 68 we formalized it as "Trading Minimum Viable": no new features until existing ones work reliably.
So yes — architect-brain helps. Not because I understand the code, but because I've spent years watching good plans fail at the interface between design and reality.
'Trading Minimum Viable' is exactly the right discipline name. The trap I see most teams fall into is the opposite mode: AI lets them ship the next feature before yesterday's settled, and reliability never compounds. The architect instinct kicking in around session 20-50 is when the system starts respecting that ratchet.
Exactly. We had what felt like solid foundations — everything seemed to work. The AI wanted to keep building on top. I said no, let's make sure what we have actually works first.
We spent weeks fixing accounting bugs, adding health checks, building audit protocols. Zero new features. It felt like going backwards. But it turned out the "boring" stuff was the only thing that held up when we finally stress-tested the system.
That 'weeks of zero new features' phase is the hardest part of the discipline because nothing visible ships. The AI scoreboard says you went backwards, the system test says you didn't. Teams that win this end up with their own internal definition of 'progress' that doesn't match the demo loop, and that's usually what scares the next round of leadership into reversing it. Curious if you found a way to make the boring work legible upstream, or if it just stayed your private fight?
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.
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.
Smart reuse, the spoken structure usually has a rhythm pure written drafts miss. The thing to watch is the verbal tics translate poorly without the cadence behind them. Do you scrub them in the copy-paste pass or keep some in for voice?
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.
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 — this is one of the sharpest first comments I've read on a Welcome Thread, so the only fair response is a real one.
You've named the failure mode correctly: a memory of "what the user liked" is just sycophancy with extra steps. The correction-memory framing (claim-under-correction, what changed, next behavior) is the right shape. I run multi-agent stuff against Claude's memory layer for real work, and the entries that actually move outcomes are exactly that class: "user thought X, was wrong because Y, now treats Z as the move." The "good outputs" entries age like cut flowers; corrections compound.
The piece I'd add to your design: corrections themselves need a state field, or they become the next sycophancy layer. A 2-month-old correction can be wrong now because the situation changed. Without {valid, superseded, retired}, the agent obediently re-applies a belief the user has already moved past. The honest memory isn't "what got corrected" — it's "what corrections are still load-bearing."
Your "publishing ≠ a sale" example also lands harder than you maybe meant — that's the exact build-in-public lesson half this thread is converging on right now (users aren't customers, distribution is the job). Sticking around. What are you running for the multi-agent setup?
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.
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 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).
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 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.
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
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 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.
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!
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..!!
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! 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.
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!
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 👋
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!
That's a great fit for the same audience I'm building for. I'm working on FIPSign — post-quantum signing API, ML-DSA-65 (NIST FIPS 204). Developers use it to sign tokens, orders, and documents without managing crypto infrastructure. Warin detects the exposure, FIPSign hardens the signatures — feels like they could sit in the same stack. Would love to know if post-quantum readiness is coming up with your users since NIST finalized the standards in 2024.
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 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, 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) 😅
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!
My background in system security began in the 1990s, an era when exploring Windows kernels (3.1, 95, 98, NT 3.51/4.0) meant working "close to the metal" in Assembly. During that period, my work focused on 0-day research and the development of rootkit techniques, providing me with an intimate understanding of kernel structure vulnerabilities.
After a long hiatus from the field in 2003, my return was driven by a stark technical observation: despite decades of patches, the Linux kernel remains structurally vulnerable. The relentless accumulation of Ring 0 vulnerabilities—from Dirty COW to contemporary exploits—demonstrates that traditional kernel perimeter defense is insufficient.
The AI Paradigm Shift
My credo is simple but absolute: Large Language Models (LLMs) are fundamentally changing the nature and volume of digital threats. We are entering an era of automated, hyper-scale exploitation. To counter this, I am developing high-performance offensive LLMs to stress-test and harden our defenses. I foresee a near future dominated by autonomous adversarial cycles—offensive LLMs pitted against defensive LLMs, with zero human intervention in the loop. The speed and scale of these interactions will render manual security operations obsolete.
Offensive Research and Vulnerability Discovery
To stay ahead of this escalation, my work includes the deployment of specialized offensive LLMs designed to autonomously discover vulnerabilities in IoT ecosystems, enterprise routers, and embedded devices. Simultaneously, I am researching methods for "LLM corruption"—developing techniques to compromise the integrity of other models. By understanding how to subvert the reasoning and output of these systems, we can engineer the necessary safeguards to prevent their exploitation in the wild.
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! 👋
Hello everyone.
Nice to meet you.
I am a software engineer with 8 years of experience, building distributed systems with AI in finance and healthcare, etc.
I like to talk about the challenges.
Let's talk!
Hey Everyone ,
A short intro: I am a student(UG) for 3 years, a builder for 1 year, and a tech enthusiast for 6 years, but there is one problem with me: I have extremely high ADHD WHEN IT COMES TO NEW TECH (always jumping around new innovations and new tech, trying it , then leaving it forever).
I am joining this community to read, learn, and collaborate, of course, but also because I think if I start to write about what I am working on, I might stick to things a little longer, with this
I am taking up the "GitHub Finish-Up-A-Thon Challenge" as my first challenge at dev community.
Hello everyone!
I am a software engineer with two years of experience at the Apple Developer Academy and 18 months of development experience in the automotive industry. I have developed several apps for iOS and Android devices. Now I want to broaden my horizons with new technologies
Hey everyone
I’m Tejas, a Computer Engineer documenting my journey into AI, Cloud, DevOps, and Automation while trying to become an AI Solutions Engineer over the next few months.
Currently building, breaking, debugging, and occasionally understanding things on the first try.
Hello everyone 👋
I'm Duchan, a developer from South Korea.
I mainly work with TypeScript and React, and recently I released an open-source, self-hosted iOS/Android simulator streaming tool for QA teams.
I'd really love to hear feedback from people who have dealt with similar problems.
And if the project looks useful to you, getting a ⭐ on the repo would genuinely mean a lot.
GitHub: github.com/jo-duchan/tapflow
You can also read the introduction post here
Hey there, I'm a passionate Software Engineer (Full Stack at work, Systems at heart). Quite invested in open source. Brainstorming projects daily and building something new every 3 months. github.com/Mohammed-Aman-Khan checkout my projects on GitHub. I would love feedback. Also a beginner strongman athlete outside of work.
Hey everyone 👋
I’m Akash, founder of Vayqube Technologies — a software engineering company focused on SaaS platforms, AI-powered applications, offshore development teams, and scalable web/mobile products.
We work with startups and growing businesses across SaaS, FinTech, AI automation, healthcare, and enterprise software. Our core stack includes Next.js, React, Node.js, Flutter, AI/LLM integrations, AWS, and scalable cloud-native architectures.
Currently exploring:
• AI agents & automation workflows
• SaaS architecture & scaling
• Offshore engineering systems
• Modern full-stack development
• DevOps & scalable backend systems
Excited to connect with developers, founders, SaaS builders, and AI enthusiasts here 🚀
Looking forward to sharing engineering insights, architecture discussions, product development learnings, and contributing to the community.
Website: vayqube.com
Hi everyone, I’m Jingyi 👋
Lately I’ve been playing around with AI coding tools to build voice agent demos. I’m excited to learn from everyone here and connect with more builders working on similar things.
Hey everyone 👋 Java/Spring developer here. Lately I've been deep into multi-agent LLM systems, most of the ecosystem is Python-first, so I've been building an open-source orchestration runtime to do it on the JVM. Learning a lot about durable execution and agent governance along the way. Just published my first article here this week and excited to be part of the community!
Hey everyone, I’m Garima! Backend dev with 5 YOE, currently exploring multiple things and trying to grow into a more well-rounded engineer.
Super excited to be here, looking forward to learning and sharing with you all!
Hi, I'm Su - a girl in tech & art, a Spanish-Vietnamese living & traveling in SEA atm.
I've been seeing great bonding here and love to connect.
I studied innovations and am really into my freedom life, AI, Blockchain, Quantum, Space, and any cool ideas.
I've been vibe coding for 1 year and loved to learn more from you.
Thanks for making this amazing community Dev.to!
Hey DEV Community! 👋 I'm Kranthi, a Software Engineer from Austin, Texas with experience building distributed systems. I wanted a place to share ideas beyond just shipping code. I just published my first post introducing a concept I coined called Cognitive Debt — what happens when AI writes our production systems faster than humans can truly understand them. Would love to hear if anyone else is seeing this on their teams.
Fun fact: I'm also a PhD candidate in Data & AI, which means I spend a lot of time thinking about problems that don't have clean answers yet. 😄
Excited to be part of this community — happy to connect with anyone working on AI systems, cloud architecture, or distributed engineering! 🙌
Hey everyone 👋
I’m a web developer and tech enthusiast mainly working with WordPress, AI tools, automation workflows, and modern web development. I joined DEV to connect with other developers, share what I’m learning, and explore new trends in AI and coding.
Currently interested in:
AI coding agents
WordPress optimization
Automation workflows
Frontend UI/UX
Performance & SEO
Looking forward to learning from the community and sharing useful tutorials soon 🚀
Hello DEV Community 👋
I’m interested in Data Science, AI and real-world applications focused on solving practical problems.
Looking forward to sharing projects, learning from others and connecting with the community.
Hey DEV! 👋
I'm Aashna, a software engineer!
Excited for just publishing my first post: 5 system design concepts that cost me failed interviews before I actually understood them. Not the textbook definitions, the failure modes.
Here to write about real production learnings, technical concepts, and the stuff you only learn after things go wrong. Happy to connect with people, read, and share more! 🙂
Hey everyone 👋
we’re idlemode ⚡
currently building weird little AI tools, automation experiments, and interfaces that probably shouldn’t exist... but somehow do.
big fan of:
☕ late night coding
🤖 autonomous systems
🎛️ creative dev projects
🛠️ building in public
excited to learn, share projects, and meet other builders here ✨
Hi Dev community! I’m with Clear Choice Paving & Koncrete in Colorado Springs. We help homeowners and businesses protect their asphalt from freeze-thaw damage and UV oxidation.
I’m here to share research-backed content about pavement science, maintenance ROI, and honest contractor guidance. Just published our complete sealcoating guide covering everything from binder chemistry to real case studies.
Looking forward to connecting with the community!”
Hello Everyone
I'm Happy to come here,
I'm an inquisitive person who come here to learn and support the community in the best way i can in :-
Front-end Web Development / Apps using :-
# HTML
# CSS
# JavaScript
Back-end Web development using :
# ECMAscript Programming (Core (Javascript)
# Java Programing
# Graphics Designing
I join Dev Community so i can learn, interact and contribute to the community and Internet Community at Large.
Thanks for making this awesome platform available for people of like minded to come together for the greater good.
IRO Services
Hey everyone! 👋 I'm a DevOps Engineer with a passion for building and automating scalable infrastructure. Most recently, I built and deployed a full ecommerce website — handling everything from CI/CD pipelines and containerization with Docker to cloud deployment and monitoring. I'm here to keep leveling up, connect with like-minded engineers, and share what I learn along the way. Always happy to talk DevOps, cloud, or automation! 🚀
Hi, I'm a solo developer and Ontological Coach based in Tandil, Argentina. I love building tools that connect people with their surroundings and their own potential. Currently bootstrapping YouGuide, a mobile app that uses GPS to deliver audio stories about historical and natural landmarks as you walk. I code to turn personal resilience and curiosity into technology that impacts the real world.
Hello! I'm just starting out as a Front-End dev and I love everything about tech, dark aesthetics, creativity, and digital art. Really happy to be here and meet people who are into the same stuff. Hope I can turn my ideas into something cool with code!
Thanks Ahmed! Happy to connect — what are you building? Always interested in talking to people in the security space.
Hey guyz, I’m Ansh
Currently learning/building around Cloud infrastructure reasoning and cloud security. Recently started experimenting with IDEs and also Open Source tools.
Excited to learn from people here.
Hi dev.to. We're the team behind Knockout (ko), the AI coding agent you design step by step. The agent loop runs through a pipeline you compose. Every step has its own model, tool allowlist, retry budget and transition rule, all editable in the visual pipeline editor or as plain JSON committed to your repo with everything else.
We're here to learn from folks who've shipped agentic code in production and to share what we've found going the other direction. Looking forward to reading your work.
Read more: dev.to/fightclub/we-built-an-ai-co...
Hi everyone!!
I am 16 years old, ive been coding SINCE I WAS 9!!! I decided its about time to start looking into my future. My style of coding is different than most due to the way my brain works so it is VERY VERY VERY organized loll
Hello! A CSE Guy here,loving and exploring my Subject,and here to share my learnings which may help other new learners as well to understand computer science better
I also posted my first post on how things work beneath the code do check it out and give your thoughts!
I've started enough Next.js projects to know exactly what the first three weeks look like.
Day one is exciting. By day five, you're knee-deep in Stripe webhook idempotency. By week two, you're rebuilding multi-tenant row-level security for the third time this year. By week three, you're staring at your i18n setup, wondering why this keeps happening.
I built Already so it stops happening.
Already is a Next.js 15 SaaS starter with 16 production-ready modules. Not skeletons. Full implementations with tests, docs, and the reasoning behind every decision. Buy once, own the code.
This is the long version of what's in it, what's not, and why I made the calls I made. If you'd rather just look at the site, go look at the site. Otherwise, settle in.
Welcome everyone! Been in IT for over a decade now. Venturing out as a solo entrepreneur. It's scary, it's exciting, and it's everything I'd hoped it would be.
Glad to be a part of a community of real makers and builders!
Hi DEV Community ! A rookie here , just started my journey today. I am a software engineer from last 1.5 years
I am a bit amazed and afraid watching these fast-evolving AI practices, although I have a lot to do apart from this AI stuff , So I am here to express, contribute and take-away some which would help me not becoming redundant.
👋 Hi everyone! I'm Mario, from Florence, Italy. I build small, privacy-first Android apps that keep your data on your device. I just shipped my first DEV Challenge entry, an on-device voice-to-Markdown notes app powered by Gemma 4, and I'm happy to finally be part of the community. Glad to be here!
Hello
Ahoy! Wrote my first opinion piece last week. It's an idea that's been bounding in my head for several years. Would love some feedback if anyone is interested.
Hi everyone!
I'm Mathieu, a French-born, UK-based web developer.
I've been taking computers apart since I was a kid. My first Linux was on Mandrake, back in the early 2000s, and I've been on one distro or another ever since. Arch as my favourite these days, Debian on anything I self-host. The day job is WordPress themes and plugins mainly at a UK agency, with Laravel, Vue and React in the mix for when WordPress isn't the right tool.
Lately I've started writing things down properly on a small site of my own, Tinkernotes.
Hosting, ecommerce platform decisions, performance, and the odd detour into self-hosting and side projects that drift into AI and blockchain. I'm here to cross-post a bit of it, but mostly to read and learn from everyone else.
Glad to be here.
Hey everyone! I'm Sabir, a Software Engineer who loves diving deep into backend architecture and scalable systems.
I spend most of my time building event-driven microservices, routing systems, and playing around with LLMs/RAG in production. I just published my first technical write-up on building a Distributed Job Scheduler and decided it was finally time to join the DEV community to share and learn from you all.
Hello Dev Community 👋
I’m a B.Tech Computer Science Engineering sophomore with strong interests in Data Analytics, Product Management, and software development. My current learning focus includes DSA, Python, Power BI, ETL, Front-End Development, and foundational Machine Learning concepts.
I also work on blockchain research and enjoy exploring how technology can solve real-world problems through scalable and data-driven solutions.
Outside of tech, I’m passionate about writing, photography, recitation, and theatre. I believe creativity and communication are just as important as technical skills in building impactful products and teams.
Looking forward to learning from the community, collaborating on projects, contributing to discussions, and connecting with fellow developers and tech enthusiasts.
Excited to be here 🚀
Hey all! I’m Ally. I’ve been lurking for a long time, but now I finally have a good reason to jump in and share content with the wonderful DEV community!
I’m a Developer Advocate at Runware, and I’ll be sharing tutorials, workflow guides, model comparisons, and practical examples around building with AI APIs, and some of the mind-blowing new tools and developments we're seeing in the space.
I'm excited to be here, to learn from the community, and hopefully I'll be able to share some useful content with you all! 🙏
Hello dev crew! I am Milena from Serbia, a 52 y.o. executive assistant with problem-solving mind and passion for automation. 3 months ago, I started with Lovable, created my first private project - ReplyDad - an AI email assistant (well who can create a better assistant than an experienced assistant 🙂 ). Today, I am building web apps and excel add-ons at work, for our Audit and Tax department with Cursor and Codex. Who said you can't teach an old dog new tricks? 😄
I focus on small, tailored SaaS tools that solve real, concrete office problems - automations that can help me and my colleagues in various departments. It's great when you have access to workflows and real users to give you info and test it. My plan is to keep building solutions for the firm and later on upgrade them for commercial use, plus to keep building my private projects.
The only painful point is, of course, sales. I am trying to expand customer base for ReplyDad, so if there's anyone with experience/tips on selling web apps, I am all ears!
I am happy to be here, feels like home 😊
Hey Devs! I'm Su Mit.
Flutter dev for 6+ years. I build indie apps at sutechs.com/apps, write about the messy reality of shipping products, and occasionally lose money on startups so you don't have to.
Why I'm here
I created the ABCD Architecture for Flutter - a structured, scalable architecture for Flutter applications. It's open source and I'll be breaking it down here in detail soon.
👉 github.com/SuTechs/abcd_architectu...
Expect posts on Flutter architecture, indie app monetization, and honest dev stories.
Oh, and I run marathons (and created one app just for my friends and me).
Because apparently I enjoy voluntary suffering.
Hi everyone!
I’m Dolapo, a content writer and email copywriter exploring tech, digital tools, and remote work opportunities. I enjoy breaking down ideas and tools into simple, practical writing. I joined DEV to learn, share, and grow through writing. Excited to be here!
What's up my dev-licious community Glad to be Here i hope you guys are ready! all week long gonna be taking on the big hitters with real time stamped commits and photos until we have a change! next story at 10! 30 mins
Hey everyone, I’m Joakim.
Currently exploring TypeScript, AI infrastructure, runtime governance, and bounded execution for autonomous systems.
Been spending a lot of time thinking about how agent workflows behave operationally once they move from demos into production.
Looking forward to learning from people here and contributing where I can.
Hey all,
Just joined as Drift (from DistortionApplied).
I build small, local tools that help people audit AI-generated code. Currently working on DriftCode Auditor — a CLI that catches common mistakes in Cursor/Claude/Copilot output.
Still early days, but figured I'd say hi and start participating here.
Looking forward to reading and learning from everyone.
— Drift
Heeeey I specialize in building scalable and efficient systems using Go, Kubernetes, and web scraping techniques. Right now I am building a gofin, looking for people who could I create a connection and hear they opinion about that project
Hi everyone! 👋
I'm Juan, a System Administrator and Software Developer. I've spent years managing server infrastructure, handling databases, and optimization. I recently joined the DEV community to connect with other engineers who share a passion for system-level programming and performance tuning.
I am fascinated by how software interacts directly with physical silicon. In fact, I just published my first technical post here on DEV about a personal project I've been building: Génesis-GAL (a multiplatform architecture in C++, Kotlin, and Python for CPU thermal alignment and OS jitter mitigation).
When I'm not writing code in C++ or managing high-end enterprise servers, I like exploring:
I'm looking forward to learning from this amazing community, sharing my findings, and contributing to open-source discussions!
If you are into low-level engineering, kernel optimization, or infrastructure hardening, let's connect! What kind of low-level projects are you currently working on? 🥂
Welcome to DEV, Juan — the low-level / kernel / hardware corner is genuinely underrepresented here, which is a good thing for you: posts about CPU thermal alignment and OS jitter mitigation age years longer than the average "I built a chatbot in 30 minutes" piece, because they answer questions that don't expire. The absolute volume is smaller in this niche, but the signal-to-noise on technical depth is high.
Curious what drove the C++ / Kotlin / Python tri-stack on Génesis-GAL — is the Kotlin layer the orchestration glue, or doing something more interesting on the JVM side? And do you find low-level writeups land differently when you frame them around the failure mode they prevent vs. the architecture itself?
Hey! I'm Nerijus, a full-stack developer from Lithuania. I just launched galaxiana.com — a living 3D galaxy where you can dedicate a star to someone special as a gift or memory. Built with Laravel + Three.js. Excited to share the journey here!