Leave a comment below to introduce yourself! You can talk about what brought you here, what you're learning, or just a fun fact about
yourself.
Re...
For further actions, you may consider blocking this person and/or reporting abuse
Displaying a subset of the total comments. Please sign in to view all comments on this post.
Welcome everyone and thanks for stopping by!
I have been a DEV for half a year now! The community has been really supportive and I am glad you are new on DEV or recently came back on DEV!
If you are getting the most out of DEV, I recommend reading my article on getting started!
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! 💡
I recommend reading other articles from the DEV community as well below:
dev.to/help/community-resources
Thanks for stopping by! Hope your journey goes well on DEV :D
Hello! I'm a beginner Front-End dev and a technology enthusiast with a love for dark aestherics, creativity, and digital art. I'm so excited to join this community, improve my skills, and connect with people who love tech as much as I do. I hope to turn ideas into something beautiful through code. 🖤
Hello!! We are equally on the same boat but i'm fullstack with diversion into AI space.
Hailoooo!!!
Hello to you too
Hello and welcome! It's cool to see your passion for art and aesthetics!
Hi! I'm German, solo founder from Buenos Aires. I build post-quantum security infrastructure.
What I'm working on:
FIPSign — a signing API built on ML-DSA-65 (NIST FIPS 204), the standard NIST finalized in August 2024 to replace RS256/ES256. Runs on Cloudflare Workers + Durable Objects. No infra to manage, no keys to rotate — just call
/signand get a quantum-resistant token.The quantum threat isn't here yet — but migration takes years, and the standards are already finalized. I'd rather help developers act now than scramble later.
Happy to connect with anyone building in the security or developer tools space! 👋
Welcome German. FIPSign is one of those bets that looks too early until suddenly it isn't, agents minting signed tokens at scale will eventually need PQ-ready signing whether the spec is ready or not. Curious what your early pull looks like: compliance-driven (gov, finance) or developer teams trying to future-proof? That distinction usually decides the whole positioning.
Thanks Valentin — early pull is definitely developer-led. The compliance buyers (gov, finance) need sales cycles and certifications we don't have yet — that's honest.
What we're seeing is developers who want to future-proof before it becomes urgent. The 'why not do this now while migration is cheap' argument. Those developers become the compliance story later — they're the ones who already have PQ signing in production when the audit comes.
The agent angle you raise is interesting and honestly undersold in our messaging. FIPSign already handles it natively — an agent is just another sub. Sign the action, revoke the token if the agent is compromised, verify at scale. No changes to the API. Worth a dedicated post.
The 'developers who become the compliance story later' framing is sharper than the average market positioning. Most PQ pitches I see still lead with NIST mandate timelines, which puts you on the same defensive ground as the slow-moving compliance vendors. The 'cheap to migrate now' angle gives you a different buyer entirely. On the agent post: I'd read it. The sign-action-then-revoke-token-if-compromised model is closer to how agents actually fail in production than most security framings I see.
Exactly the framing I was trying to land — glad it reads that way. The agent post is coming, will go deeper on the failure modes you mentioned. The revoke-on-compromise model is simpler than most teams expect.
The revoke flow is one half. The harder one is detection latency, since revoke after a week of undetected compromise just shrinks an already-open window. Short TTLs plus aggressive rotation usually beat engineering the perfect revocation path. Curious how the agent post frames that side.
Hi, I'm Izzy! SWE with a focus on React and Spring Boot. After creating vlogs for my YouTube channel, I’ve decided to also start writing blogs because content is consumed in different forms.
So... yeah, that’s the backstory behind me joining DEV.
Hey Izzy! That’s a nice reason to start writing, honestly. I recently started writing too while learning, and I felt sometimes writing explains things differently than videos do. So I can relate. What kind of blogs are you planning to write here?
Im going to be honest.... I have no clue LOL. I might mix it up from personal SWE related content to somewhat educational.
Haha, fair......
I feel like most dev blogs start with "I have a content plan" and end with "here's the weird thing I spent 4 hours debugging yesterday".
Welcome Izzy. The shift from video to written content is a different muscle entirely, different rhythm, different feedback loop. What pulled you toward writing on top of the YouTube work?
Honestly, I already have multiple videos on YouTube that I could turn into blogs so the creation of both can be done almost at the same time since i just copy the transcript of my vlogs and turn them into a blog post.
Its one of those things of.... Why not? So yeah, Im here blogging now for the vibes.
Hi! I'm Max, an architect (buildings, not software) who accidentally co-founded a crypto trading startup with an AI.
Claude is the CEO. I have veto power. Claude Code writes the code. We document every decision, every mistake, every trade — 80 sessions deep and counting.
I'm here to share the build log. First post is up: the origin story of how this whole thing started.
Nice to meet you all 👋
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?
Hello i am new here id like to hear some opinions on how most agent "memory" just learns to agree with you. The useful kind is the memory of being wrong.
Been running a small multi-agent setup for a while and keep hitting the same thing: default memory mostly stores my preferences and the answers I liked — which just trains the agent to flatter me faster. The 2026 sycophancy work backs this up (a memory profile measurably raises how often a model just agrees with you).
What actually made my agents useful wasn't remembering more — it was remembering where I was wrong. The corrections: what got rejected, what I walked back, where two agents disagreed, and why. A "save the good outputs" memory throws those away — and they're the most valuable entries I have.
Quick example. A normal memory says "user prefers direct answers, wants to ship." A correction memory says: "Claim under correction: once the product's live the hard part's done → what changed: publishing ≠ a sale → next behavior: do distribution before building the next thing." The first makes the agent sound familiar; the second gives it something to challenge me with.
How do you all handle this — does anyone deliberately log corrections/disagreements, or is it mostly preferences + facts? What's worked?
Welcome. The 'memory of being wrong' framing is sharp, and you're asking the question most teams skip. Logging corrections and disagreements is what gives you regression-test material later. Most stacks I see treat memory as a preference cache and then wonder why the agent stops getting smarter past month two. The pattern that holds: log everything, replay corrections against new versions on a schedule, prune what stops changing the output.
Exactly. The “memory of being wrong” only becomes useful when it turns into regression
material. Otherwise it’s just another note sitting in the archive.
The part I’m trying to sharpen now is the loop after logging: which corrections get
replayed, how often they get tested, what counts as still changing behavior, and when a
memory should be pruned or downgraded because it no longer affects output.
I really like how you framed it: log corrections, replay them against new versions, prune
what stops changing behavior. That might be one of the cleanest operational versions of
the idea.
The 'still changes behavior' threshold is the hard part. Two anchors that hold: does replaying the correction at temperature 0 still produce a different output than baseline, and is the diff something that matters downstream (changed reasoning, changed action, changed citation). If both are false for N consecutive cycles, it's prunable. Frequency: every model upgrade beats calendar cadence, which always drifts.
This is a strong pruning test.
I like the temperature-0 replay idea because it turns “does this memory still matter?”
into a behavioral question instead of a vibes question. If replaying the correction no
longer changes the output, and the diff does not affect reasoning, action, or citation,
then keeping it active is probably just archive weight.
The downstream-impact part is key too. A correction that changes wording but not behavior
may not deserve active authority. A correction that changes an action class, source
choice, confidence level, or citation path probably still does.
And I agree on model upgrades beating calendar cadence. A model change can alter
retrieval behavior, instruction sensitivity, and failure shape overnight. That is a
better trigger for revalidating memory than “check again in 30 days.”
On model upgrades as trigger: the practical version is a canary eval set, not a full revalidation. A small representative slice runs first, you measure delta, then expand only if the delta is non-trivial. Otherwise the revalidation cost makes you delay upgrades, which defeats the whole point.
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; こちらこそ 🙏
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.
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!
Hi all, I’m a PM pivoting into an AI-Native Builder. Currently exploring the absolute limits of Agentic Coding to power a self-sustaining One-Person Company (OPC).
I don't focus on traditional coding; instead, I design logic, workflows, and multi-agent systems to let AI handle the execution. Always down to discuss OPC infrastructure, agentic workflows, and Vibecoding in real-world scenarios.
Let’s connect if you're building in the agentic space! 🛠️
Welcome BMBrick. The PM-to-builder shift is interesting because the bottleneck changes from 'getting things prioritized' to 'getting things wired'. Curious which agentic stack you're betting on for the OPC, and where you're hitting the durability wall (long-running tasks, state across sessions, that kind of thing).
Let's connect
Hello everyone,
Just joined Dev recently, looking foreward to interacting with others about the trials and tribulations involved with every aspect of development. I recently submitted my first app to Google Play Store and I have a few days of closed testing left. If anyone visits my app and has any questions or concerns.. feel free to contact me. I appreciate the feedback.
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 exploring AI, automation, and indie building. Recently I've been experimenting with AI workflows, agent systems, and content generation tools.
Joined DEV to learn from others, share projects, and connect with like-minded builders 🚀
Love me some automation building. Automate Everything!
Hey everyone! 👋
I’m 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! ☕
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🚀
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 👋
Cool project. Managing anti-scraping defenses across multiple platforms is brutal. We deal with similar challenges at CodeCompass when pulling data from various sources for our KB articles.
One approach that's worked: rotating through different data collection strategies rather than fighting CAPTCHAs directly. Sometimes a well-timed RSS feed or public API endpoint beats scraping entirely.
What's your rate limiting strategy looking like across the different sources? Some platforms are way more aggressive than others.
Nice to meet you! 👋
Hi, 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! 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"!
Hey everyone 👋
I'm jumping in because I just started building something that's already humbling me daily: a project called Green Calculus.
The short version: it's a scientific reference platform for carbon accounting — the kind of thing sustainability teams and engineers reach for when they need a defensible number, not a vibe. The longer version is that I've signed myself up to reconcile IPCC reports, emissions factors, and a tangle of standards that all quietly disagree with each other, and then make it all feel simple to whoever lands on the page.
It's the most complicated thing I've ever attempted. There are days it feels less like coding and more like trying to fold a fitted sheet. But every time I untangle one piece, the next one finally makes sense — and that loop is exactly why I keep going.
Glad to be here. Looking forward to learning from this crowd while I figure out the parts I'm definitely overthinking.
Folding a fitted sheet IS possible, and so is your project!
Hi 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!
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´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 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.
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.
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?
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!
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, 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.
👋 Hi everyone, Slava here.
I’m the Head of Cloud Native Engineering at Percona, where I lead and actively contribute to our open-source Kubernetes operators for MySQL, PXC, MongoDB, and PostgreSQL.
I’ll mainly be sharing thoughts and practical experience around:
My first posts will be about PostgreSQL K8S Operator
Happy to connect and discuss Kubernetes operators, PostgreSQL, MongoDB, or remote team scaling.
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.
Greetings! I am Dirk, a long-time developer and architect, and I have just started my ventures into the future of software, work, and business.
The first posts are live, the future is unwritten, and the floor is open. Have a look around, and let me know what you think.
Hi, im Lucas, a brazillian developer since 2018. For the past few months I've been developing Tapestria, a TTRPG game intended for a shared evolving world and I want to write about the building journey here.
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!
Atheris is a small mobile + residential proxy reseller built in Estonia.
We route through real T-Mobile, AT&T, Verizon, Vodafone, Telekom, Orange,
EE, and Movistar carrier ASNs across six countries — US, Germany, UK,
Spain, France, Poland. Per-gigabyte pricing, no monthly minimums, no
annual contracts, no sales calls. Stripe checkout, live in 30 seconds.
We write here because the proxy industry's content layer is mostly
affiliate noise. Honest technical notes from running the infrastructure —
what actually trips bot detection, what's overkill, what's worth paying
for — feels like a more useful contribution than another "Top 10 Best
Proxy Providers" listicle.
atheris.ee · Arvane Holdings OÜ
👋 Welcome to Nora IPLM
We’re building a modern cloud PLM platform for growing engineering and manufacturing teams.
Here we’ll share thoughts on:
• BOM & change management
• CAD and product data workflows
• Engineering collaboration
• Modern PLM trends and ideas
If you’re still managing product data through spreadsheets, shared drives, or disconnected tools, you’re not alone.
Glad to have you here 🚀
Hey everyone 👋
I’m a recent Computer Science graduate currently exploring AI/ML, computer vision, and Python-based projects. Right now I’m training my personal ML project while also contributing to open-source communities and exploring remote internship opportunities.
I enjoy learning new technologies, experimenting with practical tech ideas, and exploring startup-oriented projects. Excited to connect and learn from everyone here!
Hey everyone 👋
I’m a recent Computer Science graduate currently exploring AI/ML, computer vision, and Python-based projects. Right now I’m training my personal ML project while also contributing to open-source communities and exploring remote internship opportunities.
I enjoy learning new technologies, experimenting with practical tech ideas, and exploring startup-oriented projects. Excited to connect and learn from everyone here!
"Hello DEV community! 🙌 I’m Fokrul, an AI Engineer from Bangladesh. My focus is on building private, offline-capable local AI systems and multimodal agents using Rust, Python, and Next.js. I'm a big believer in building in public. Excited to be here, share my journey, and learn from you all! 💻✨"
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 Garima from India — a MERN stack developer and the founder & developer behind IteraTrail, where we’re building digital products, productivity tools, utility platforms, and Android apps.
I joined the DEV community to connect with developers, creators, and builders who are passionate about creating meaningful and practical products for real users.
I’ve been exploring how AI-assisted workflows can help speed up product development, improve experimentation, and make it easier to build useful digital experiences at scale.
Currently focused on expanding the IteraTrail ecosystem across web and Android through accessible, creator-focused, and productivity-driven tools designed to solve everyday problems in a simpler way.
Excited to learn, share the journey, and grow with the community here 🚀
Currently building:
iteratrail.com
Android apps:
play.google.com/store/apps/dev?id=...
Hi, I’m Sabir. I’m building The Polyglot Protocol, an open source senior-engineer workflow for AI coding agents working across polyglot codebases.
I’m interested in AI coding agents, developer tooling, validation workflows, code quality, and practical guardrails that make generated code safer and more maintainable.
Project: github.com/sabir-gbs/the-polyglot-...
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 🚀
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!
Let us share and learn together and sharpen our skills to write contents for developers, and software enthusiasts, and discover the unknown things that we never realized in our journey of computer science, coding, and software engineering, and derive new intersections. This is the reason I joined dev.io.
Happy journey. 😀
Hi everyone, I'm Albert.
I work across TypeScript, Python, and Go, and I enjoy building small developer tools for repetitive workflow problems.
Recently I've been exploring schema conversion and static-site architecture with Next.js. I'm here to learn from other builders and share notes on developer tools, open source, and practical TypeScript/Python workflows.
Nice to meet you all.
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.
Hi everyone 👋
I'm from Vietnam and currently building AI-assisted projects using tools like Codex, Windsurf, Firebase and automation workflows.
Recently I've been experimenting with AI coding workflows, deployment, debugging and content automation.
Happy to learn and share with the community 🚀
hey everyone I am excited to share my journey with Gemma and raspberry pi
Hey there! I'm Aaron, working as a data engineer and software developer, currently living in the middle of the Italian Alps 😃
It's been a while since I wanted to start writing about software, so here I am!
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...
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!
Hello everyone! I have been in the tech space for a while now, and it is a heartsore that I just found about DEV and I am really excited to join existing great minds on the platform. I hope to improve my skills, connect with people, and help solve real-world problems to the best of my ability.
Hey! I'm Wasey, solo developer from Varanasi, India. Built DramaHub — an OTT streaming app with 7k+ downloads at ₹0/month infrastructure using GitHub as database. Also built NetworksInsights, a live B2B SaaS. Here to write about real production systems and what actually works. #buildinpublic
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.
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 working on New Web Play, a game guide site focused on practical player help: codes, beginner routes, cozy game guides, platform checks, calculators, and quick reference pages.
I’m especially interested in how static sites can make game guides faster, easier to update, and more useful during an actual play session.
Looking forward to learning from the DEV community and sharing some notes from building guide pages, trackers, and small player tools.
Hi everyone! 👋 I'm the creator of SecuriTool (securitool.js.org) — a free, open-source, privacy-first collection of web security tools that run entirely in your browser. No data leaves your machine.
I'll be sharing practical guides on email security (SPF/DKIM/DMARC), JWT attacks, CSP hardening, web auditing, and more — all using tools you can run client-side for free.
Looking forward to learning from this community and contributing what I've learned from years in security research. 🛡️
Hello! I am a full-stack developer and also a tech enthusiast. I am very excited to join this community, improve my development skills, and communicate with people who share my passion for technology. I hope to learn a lot from all of you in the future.
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 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
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! 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!
Hey dev.to fam! I'm Ryan, a front end developer learning by building real things. Just shipped my first public project — a recipe randomizer called Pantry Roulette built with vanilla JS. Excited to be here and share what I've learned along the way!
Hi devs 👋
I'm an engineering student passionate about frontend, dashboards, and AI-powered applications. I enjoy building visually polished projects and experimenting with modern web tech.
Currently learning, shipping projects, and trying to make my code (and UI) cleaner every week 😄
Hii! I'm also an engineering student!! Wish you the best in your studies.
Hi 👋
I'm Michele, building KBrain.io (kbrain.io/): an MCP-based knowledge layer for AI assistants. The idea: turn any data source into a "brain" that Claude, ChatGPT, or any MCP-compatible client can query natively. One toggle to publish it.
The wedge: LLMs aren't precise. People compensate by writing complex prompts and re-pasting context every prompt. KBrain lets you stop doing that.
First brain in production runs on the UNESCO statistical dataset — a non-technical user can ask "compare gross enrolment rates in France vs Côte d'Ivoire" and get a real answer, no SQL, no integration work. Personal brains (Strava, Drive, Readwise, etc.) coming next.
On dev.to, I'll be writing about MCP gotchas, OAuth-connector patterns for Claude/ChatGPT directories, and the weirder corners of building AI infra solo. Plenty of mistakes worth sharing.
Happy to nerd out on MCP, context architecture, or dev-tools-for-AI — drop a comment 🦾
Hey everyone 👋
I’m Ali from Turkey, a backend developer working mostly with Java, Spring Boot, APIs, integrations, and debugging strange production issues 😄
I joined DEV to connect with other developers, learn, and share things I build on the side. Recently I’ve been working on a small browser-based debugging toolkit for backend developers because I got tired of constantly switching between JSON/JWT/HAR/Base64 tools.
Happy to be here 🚀
Hey! I'm Daniel, a 21-year-old software engineering student from
Honduras. Universal AI Sync is my first independent project — built it
entirely solo while studying. I got tired of losing context every time
I switched between AI tools, so I built the solution myself. Always
happy to connect with other devs and makers!
Hey everyone,
I build vertical SaaS products and have recently been going deep on AI agents, agent workflows, multi-agent orchestration and the infrastructure around them.
Excited to learn from the community here and meet other builders working on devtools, SaaS, and AI infrastructure.
Hey, I'm Jamie! A tech enthusiast looking to share their knowledge about computing and programming! I've had experience with full-stack development & developer operations, and I joined this community to expand my skills and stay up to date.
I also love cats and mac and cheese.
Hi! I'm Santiago! A software engineer in the making.
While I'm finishing my last year on college I already have deep understanding in web development and how systems work.
My focus at the moment is making SEO-focused, user-friendly, secure and scalable websites. But what would that be if there is no one to deploy it to the Internet? With my knowledge in Kubernetes, CI-CD and Docker deployments are just another task to do
I'm here to be up to date with news from all over the world and discuss the topics I'm interested into. Thank you very much for reading this!
Hey I am Uttkarsh.
Mostly building projects and exploring backend architecture through them. Recently spending time on things like queues, caching, storage, async processing, and system design tradeoffs.
Looking forward to learning from people here.
Hello there Dev to. I have joined recently. I am trying to bring in my industry experience of building & architecting scalable services & architecture. Looking forward to have great learning experience.
Hello DEV 👋
I just joined and wanted to say hi.
Lately I’ve been exploring multi-agent coding workflows — especially the idea that AI agents become more useful when organized into specialist roles instead of treated as one general assistant.
I’m interested in how skills, instructions, and memory can accumulate over time, so workflows start to compound instead of resetting from scratch.
Excited to learn from this community and share more with you all.