Welcome to VibeCoders

Saw a thread on r/vibecoding yesterday about apps shipping with exposed endpoints and unprotected user data. It’s a wake-up call we need to address head-on. This isn’t just about friction or the learning curve—it’s about understanding what vibecoding actually is and isn’t. Vibecoding is: • Using LLMs to scaffold MVPs and sketch out ideas rapidly • Skipping monotonous boilerplate with AI and CLI agents • Learning CS concepts through conversational exploration • Building faster, iterating quicker, prototyping fearlessly Vibecoding is not: • A magic deployment button • A substitute for understanding your stack • An excuse to skip security fundamentals • A way to avoid the craft of software engineering The real power of vibecoding comes from amplifying your skills, not replacing them. When you generate an API endpoint, you still need to understand authentication. When you scaffold a database schema, you still need to think about data protection. When you deploy to production, you still need to secure your application. The friction isn’t a bug—it’s a feature. It’s the space where learning happens, where you turn generated code into production-ready software, where you become a better engineer. We’re not just building apps faster; we’re building ourselves into developers who can harness AI while still shipping secure, maintainable code. That’s the real vibe.​​​​​​​​​​​​​​​​

There's an interesting concept I've noticed in the LLM/Prompt Engineering space, and that's getting an LLM to write a prompt for you, better than you ever could. Most of us have done this, and seen just how good AI understands *itself*. This is especially important when integrating agentic workflows, dominated by an LLM, in development and engineering. I've found it especially helpful to use multiple Language Models at once to bounce off of one another - a common practice - but I've taken this a step further by asking agentic workers to prompt APIs that use ai and prompting better than I ever could - taking that concept and turning it into an agency machine. When a machine is prompted to give instructions to another machine, specifically relating to agency, it seems to work wonders. Has anyone else experimented with this?

idk if this is just me but does anyone else get way too in their head when coding? like you spend 3 hours refactoring a function that already worked fine because you read some blog post about "clean code" or whatever been working on this dumb project and i keep catching myself doing this. like i'll write something, it works, but then i'm like "hmm this isn't how they do it at google" and i rewrite the whole thing. rinse repeat until i hate everything. but sometimes i just turn off my brain and write whatever. put on some music, stop checking stackoverflow every 5 seconds, and just type. and weirdly those are the times when i actually get shit done? like last week i was trying to parse some janky json and kept trying to make it "proper" with error handling and type checking and all that. spent forever on it. then i just said fuck it and wrote the most basic ugly parser and it worked perfectly. took like 10 minutes. that's what i think vibecoding is - just writing code without overthinking every line. not saying we should all write garbage code, but sometimes you gotta trust your gut instead of trying to impress some imaginary senior dev looking over your shoulder. anyone else deal with this? feel like i see a lot of posts about imposter syndrome but not much about just... letting yourself code badly sometimes and being ok with it. also kinda wondering if this is why i code better at 2am when i'm too tired to overthink everything lol

prompts, ideas, projects, CLI workflows, lets talk about it. post your stuff!

I made a tool where you enter any business and apis do an analysis on how trustworthy the business is! check it out for free! https://v0-business-reputation-tool.vercel.app

Automated Foreign Currency and Stock Data Scraper. vibecoded this in like 20 mins just to see what i can do with half an idea and creative energy. I run it whenever im interested in investing/the market, but if it gets users i will run it daily/cron it.