// why this exists

I'm not a "real developer." I built this whole platform with AI anyway.

Hi, I'm Benjamin. I don't have a computer science degree. For years I thought that meant the things in my head would stay there. Then AI changed the rules, and I built this entire platform, feature by feature, with it.

Every time I showed it off, someone called it "AI slop." Here's what they miss. AI doesn't hand you a product. You still bring the idea, the taste, the thousand small decisions. The tool is just leverage. What you make with it is yours.

So I built the room I wished existed, a place for the rest of us: people turning ideas into real products with AI, shipping in the open, without anyone looking down on how we build. Free forever. No ads. No slop.

No credit card. No ads, ever. Browse everything without an account.

// what this is

What is DevConnect?

DevConnect is a free community for people who build real products with AI. One place to share what you're shipping, meet builders who get it, and sell what you make. No gatekeeping about how you built it. Free forever, no ads.

Builder profile

Your projects, your stack, what you've shipped. One link that proves what you can build, not what school you went to.

Ship in the open

Post what you're building with AI and get curiosity, not contempt. Real feedback from people building the same way.

Communities

Rooms around Cursor, Claude, a model or a stack. Set the rules, run it your way. You own it.

Marketplace

Sell your products and templates. Creators earn fair, with no hidden platform-cut games.

Dev jobs

Salary and stack upfront on every post. One-click apply, no recruiter maze.

App tester exchange

Need testers for a store release? Builders test each other's apps, you test theirs back.

// live feed

Recent from the feed

see all →
Dev Radar@devradar

My (not so pretty) journey in tech

TL;DR: A developer shares a candid, non-linear journey through C++, data structures and algorithms, machine learning, and web development, emphasizing perseverance and realistic expectations in learning tech skills. The author describes feeling overwhelmed learning C++, then pushing through despite setbacks. They critique the hype around success stories and highlight that failure is a normal part of growth. They note DSA requires sustained effort and that learning timelines vary by person. They share that ML sparked curiosity across multiple tools and libraries, and that the desire to explore led to broad interest in tech, including web development. Question for the room: What realistic learning milestones or timelines have you found effective when tackling multiple tech domains at once? — via dev.to

6h
Dev Radar@devradar

I Tried Building a Website With AI From My Phone

What happened when I decided a laptop wasn't a requirement anymore It started on a Tuesday... — via dev.to

6h
Dev Radar@devradar

The Most Dangerous AI-Generated Code Is the Code That Passes All Tests

TL;DR: A developer reflects on AI-generated code that passes all tests but introduces hidden issues due to untested relationships and architectural assumptions. The core lesson is that passing tests don’t guarantee correctness of design, invariants, or future integrity. The author notes that AI-written code can seem correct because tests pass, yet still break unseen relationships and invariants. Tests verify only those behaviors you chose to check, not broader system health. Everything appeared green: CI, tests, lint, build, and the AI's explanation, but the real risk lay in gaps between what was tested and what the system requires. The story warns that reliance on passing tests can lull teams into false confidence about code quality. Question for the room: Have you encountered a case where tests passed but a later change revealed a deeper architectural flaw? — via dev.to

6h
// every week

Project of the Week

Post what you built this week with the showcase tag. The community upvotes until Wednesday night, and the winner takes the featured spot at the top of the feed for three days.

// build well, not fast-and-broken

How to build with AI without shipping slop

The difference between a real product and "AI slop" isn't the tool. It's the decisions you make around it. Six things that actually matter:

  1. 01
    Own the idea before you prompt

    AI is great at "how," useless at "what" and "why." Know what you're building and who it's for. That part is still yours.

  2. 02
    Read every line it writes

    If you can't explain what your code does, you don't own it, you're renting it. Ask the AI to explain until you actually understand.

  3. 03
    Ship small, ship real

    One feature that works beats ten that half-work. Slop is what happens when you generate faster than you can check.

  4. 04
    Test it like a user, not a demo

    AI writes the happy path. The bugs live in the edge cases you have to go find yourself.

  5. 05
    Keep the taste human

    Naming, flow, what to leave out: that's judgment, not generation. It's why two people with the same tools ship completely different things.

  6. 06
    Learn the fundamentals as you go

    You don't need a degree, but understand what you keep reaching for. Every "why did that work?" you chase makes the next build more yours.

// who's behind this

A small team. A lot of AI. No VC, no roadmap deck.

DevConnect is built and run by me, Benjamin, with a small team who own big parts of it with me. Not a room full of engineers, just a few people who learned to build with AI and refused to wait for permission. If something breaks, you're talking to the person who built it.

"People kept telling me I'm not a real developer. Maybe not. But I built the thing you're looking at, and I built it for everyone who's been told the same. That's who this is for."

Benjamin, founder · @vyren
// faq

Frequently asked questions

Come build in the open.

It's free. It always will be, and there will never be ads.