u/Friendly_Gold3533

I'm not a developer. Like at all. I failed my one CS class in college and told myself coding just wasn't for me.

But I had this idea that wouldn't leave me alone. A simple tool for something I dealt with every day at work. Nothing fancy. Just something that would save me like 20 minutes every morning.

So I tried.

First two weeks were genuinely humbling. I'd get something working and break it trying to add one small thing. Ask the AI to fix it and it would fix that and break two other things. I had a moment where I opened my laptop, looked at the screen, and just closed it again and went to watch TV.

I told my friend I was building something and he asked to see it. I said it wasn't ready. It wasn't ready for three weeks lol.

The turning point was honestly just getting stubborn about one single feature instead of trying to make everything work at once. Stopped trying to build the whole thing and just got one button to do exactly what I wanted. Then another. Then another.

Last Tuesday I opened the browser and used my own tool to do the thing I built it for. First time. Worked exactly how I imagined it.

Sat there for a second kind of not believing it.

I'm not saying it's good. The UI is rough and I'm sure a real developer would laugh at the code. But it exists and it works and I made it.

That felt like enough for one month

So this is kind of embarrassing to admit but I spent the better part of last year building things that nobody used.

Not because they were broken. They worked fine. I'd vibe code something over a weekend, get it running, share a GitHub link in a discord and get maybe 3 upvotes from people who never actually tried it.

I thought I just had bad ideas. Kept moving to the next one. Same result every time.

Then someone in a thread roasted my landing page and it kind of broke my brain a little. It was just a login screen. No explanation of what the thing did, no reason to trust it, nothing. Just "sign up" on a white background. I genuinely did not realize this was a problem because I was so focused on the code being good.

The product was never the issue. The packaging was.

Started spending as much time on the landing page and the messaging as I did on the actual build. First project after that got real signups from strangers. People I didn't know, didn't ask, just found it and tried it.

Vibe coding made building fast but it also made me forget that shipping is not the same as launching. A working app sitting behind a confusing page is just a private project with a domain name.

Anyway hope this helps someone who's sitting on a graveyard of repos wondering what they're doing wrong. It might not be the code.

So I've been in the no-code space for about two years. Bubble, Webflow, Glide, Softr, you name it I've probably broken something in it.

Last month I had a client who needed a simple internal tool. Nothing crazy. A form that captures leads, routes them to the right team member based on some criteria, sends a follow up email, logs everything in a sheet. Classic stuff.

I quoted two weeks. Took three because the Bubble workflow logic kept doing something weird with the conditional routing and I couldn't figure out why for the life of me.

Then last week I needed to build something similar for a different client. Same general idea, slightly different logic.

Tried a different approach this time. Described the whole thing to Claude, let it ask me questions about edge cases I hadn't thought about, and then built the whole thing in Make with the logic already mapped out clearly before I touched a single module.

Done in a weekend.

Same complexity. Fraction of the time.

The weird feeling is that I didn't really learn anything new. With no-code I always felt like I was building a skill. Now I'm not sure what skill I'm building exactly.

Anyone else navigating this? Like does the no-code background still matter or are we all just becoming prompt engineers who happen to know what a webhook is?

Not complaining. Just genuinely curious where this is heading.

When I started I thought the hard part would be not knowing how to code. Turns out that's not really the hard part.

The hard part is that AI will confidently build you exactly what you described and it will be completely wrong for reasons you didn't know to describe.

Like I spent a whole week building a dashboard that "worked". Users could log in, see their data, filter it, export it. Everything worked. Then someone logged in as a different user and saw the first user's data. Classic IDOR bug. Never occurred to me to test that because I was testing as myself.

Nobody tells you that vibe coding is actually just product management with extra steps. The AI handles the syntax. You still have to know what you're building and why and what could go wrong. That part doesn't get automated.

The sessions that go well are the ones where I spend 20 minutes writing down exactly what I want before I open Cursor or Claude Code. The sessions that turn into 3am disasters are the ones where I just start prompting and figure it out as I go.

Also the first time Claude deleted something important and I had no version history was a formative experience I don't recommend to anyone.

What's the most expensive lesson you've learned the hard way?

not looking for sympathy just want to document this for anyone else who has lost their mind over something stupid.

built a form submission handler that was working perfectly in development. deployed it and it broke. completely. no useful error message just a silent failure that returned a 200 status and did absolutely nothing.

checked the database. checked the api routes. checked authentication. rewrote the whole handler twice. read the documentation three times. asked three different ai tools and got three different wrong answers.

day three. found it. missing semicolon in a config file that was somehow only causing issues in the production environment because of how the build process handled it differently.

three days. one semicolon.

i have been doing this for four years and it still happens. the experience does not make you immune it just means you have more places to look before you find the stupid thing.

anyone else have a recent one that made them question everything

i am not a developer. i took one python course two years ago and forgot most of it. three weeks ago i decided to just start building something using cursor and claude and honestly just vibing through it.

i did not plan the architecture. i did not write tests. i googled everything. i asked ai to explain error messages i did not understand. i copy pasted things i only half understood and moved on.

last week i shipped it. it works. real people are using it.

the thing nobody told me about vibe coding is that the embarrassing part is not the code. the embarrassing part is realising how much of software development was gatekept by the idea that you needed to understand everything before you could build anything.

i still do not know what half my code is doing at a deep level. but it runs and it solves a problem and people find it useful.

curious how many people here came from a non technical background and just decided to start anyway. what did you build first