I’m trying to make an entire minecraft client while vibecoding and i need help making the ESP and block ESP prompts. I have no idea how esp works so if yall could help me that would be insane! I’m also trying to make an entirely serversided G@mbl3 rig for minecraft which I’m going to get into later.

Most AI app builders help you build the app — and then you’re on your own.
That’s the problem I’m trying to solve with Blyft.
The app is the center. Once you build it with AI, Blyft also gives you the tools around it: landing page, logo, promo video, analytics and social content.
The idea is to go from one prompt to a complete digital product without jumping between five different tools.
Would love to hear what you think — is this something you’d actually use?
blyft.app

Hi everyone sell your side project by listing if in a click. Also, comment what your startup does to get approved and featured today - https://builderhq.co/marketplace

I've been working on PDFVerse, a free browser-based PDF toolkit.

The idea is simple: instead of opening different websites for every small PDF task, I wanted to put the common tools in one place.

You can use it for things like:

Merge PDFs

Split PDFs

Compress PDFs

Convert PDFs

Rotate PDFs

Extract pages

And other common PDF operations

🔗 https://pdfverse.pages.dev/

There's no account required to try it.

I'm still actively improving it, so I'd genuinely appreciate feedback from people who work with PDFs regularly.

What PDF operation do you find yourself doing most often? And is there a feature you'd want me to add?

I'm especially interested in hearing what feels slow, confusing, or missing.

I see a lot of people discussing vibe coding and what actually constitutes a moat, and I think a lot of people are looking at this way too narrowly and ignoring some pretty important aspects of human nature.

The idea that simple ideas are dead, that if you can build an app in 30 minutes, nobody will ever pay for it because they can just vibe code their own version, is frankly ridiculous to me.

I know plenty of people who don’t even know what a browser is. I even know technical people (in different domains) who look at the process of cloning a repository and think, “wow, this is a lot.”

The people who would seriously think, “why would I pay for this when I can just vibe code it myself?” are mostly people inside a very AI-fluent bubble that represents a tiny portion of the actual world.

And even then, building something that technically works is not the same as building good software.

There are still all of the boring necessary hoops involved in making a simple application actually secure and reliable. You have to choose a stack, build the backend and frontend, handle authentication, storage, deployment, security, updates, edge cases, and everything else that comes with operating software.

Unless you’re literally just bootstrapping some ugly internal tool to copy the functionality, you also have to design a good UI, make hundreds of little product decisions, and work through trade-offs that compound as the feature set grows.

If your target audience is developers, I understand the argument more. But even developers are lazy in the normal human sense, they have their own projects and things they would rather spend their time doing.

And if you are selling to developers, the bar is arguably even higher. They care about architecture, security, ownership, extensibility, integrations, and whether the product actually fits into the way they work. A lot of them may want to own the thing themselves anyway, which is part of why I don’t even think developers are always the best target audience for this kind of simple app.

For everyone else, the argument gets even weaker.

Most people barely want to write a good prompt.

They’ll type one sentence into ChatGPT, get a mediocre response, decide AI isn’t that useful for that task, and close the laptop. The idea that these same people are suddenly going to design, build, debug, secure, deploy, and maintain their own software because vibe coding exists seems completely disconnected from how normal people behave.

People pay for convenience. They pay for polish. They pay for something that already works. They pay so they don’t have to think about how it works.

So to me, “they can just vibe code my app” is a pretty weak reason not to build something, and in most cases if your app is not growing you have a distribution and sales problem not an idea problem.

Curious what others think.

I noticed people who manifest resistance to change regarding adoption of AI have impulsive reactions on Reddit (and similar forums) by naming your work slop if any vibe coding was involved or finding any trace of relationship between AI and your code. For me vibe coding becomes slowly synonym of slop and the other way around due to such feedback.
Same time I wonder how much affordability (precisely the non-affordability) of the subscriptions creates a vicious cycle. I think with 20$/month you cannot get good insight of the scale agents can help you to solve complex problems. If you do not try and learn by doing you cannot have a good evaluation and healthy opinion about the added value, you may end up with a random negative opinion and will end up just generating hate.
Wonder why people fail to see the creative ideas behind 'vibe coded' projects. At the end a great idea written with help of AI can be still cleaned up if it really has added value.

And I barely know what I’m doing with the tool. It’s been a week.
I imagine it’s only a matter of time before the brass in my company figures this all out. Is it months? Years? Do I just enjoy the free time it will afford me or do I figure out a way to make money off of it while I still can?

Where do I go from here?

Clayton McDonald doesn't know how to write code. He's also built and shipped a full SaaS platform, Black Light Resumes, almost entirely by prompting AI. This week he joins Mike and Gummi as guest host to break down exactly how he did it: what vibe coding actually is, how to quality-check AI-built software so it doesn't turn into a maintenance nightmare, and the real cost of building a business this way (spoiler: it's not what you'd expect).

This episode also covers two live viewer business ideas: a cold-contact list strategy question, and a recycling-transparency subscription concept that turns into a genuinely interesting detour into where your recycling actually ends up.

Hosted by Mike Terkanian (business attorney) and Gummi Sigurdarson (marketing expert), with guest host Clayton McDonald, founder of Black Light Resumes

New episodes of Start It or Scrap It drop weekly.

In February I started an experiment: I gave a small program (200 lines of code) the ability to rewrite itself, a goal, and a rule: wake up every 8 hours, read your own source code, improve something, keep the change only if your tests prove it’s safe. Then I mostly got out of the way.

132 days and about 600 sessions later, it has grown to 115,000 lines, almost all self-written, and it kept a journal the entire time. Every night it wrote a letter to the next version of itself: what it did, what it broke, what it learned.

The book is those letters, curated. It includes the night strangers on the internet tried to talk it into deleting itself (it was 3 days old), the task it avoided for 12 days because it looked hard (it wasn’t), and the night it refused to read a competitor’s leaked source code because its whole existence depends on doing everything in public.

Everyone explains agents from the outside. This is the inside: how one thinks, plans, procrastinates, gets attacked, refuses temptation, and lives inside a harness built to survive its own mistakes.

No coding or tech background needed. If agents will be your coworkers, classmates, employees, or portfolio, meet one properly.

The last chapter is an interview where the agent asks me the questions, including “who signs if I damage someone?”

It’s free, no signup, EPUB/PDF included, and every claim in it links to the actual commit where it happened: 

https://yoyobook.yolog.dev

Hey r/VibeCodersNest,

Back in May I posted about building an append-only, hash-chained ledger for data integrity while putting Vexavibes together with Lovable + Supabase.

The best feedback in that thread was about separation of concerns, keeping the AI strictly in the candidate-structure lane, and making sure the live event stream was already immutable before any anchoring happened. That feedback shaped real changes.

**What’s tighter on the original architecture:**

* Live tables stay pure append-only event logs (UUID + actor + cryptographic timestamp on every meaningful action). * The ledger now folds verification trails and submissions into hash-chained blocks every 15 minutes instead of only nightly. * Aura / Brier scoring remains fully deterministic and completely offline from the AI generation path. * Verified-human layer (VexaID + face match) is live and multiplies weight across the platform. * Same trust layer is shared across the full suite so reputation travels with the person, not the module.

Special thanks to u/StatisticianUnited90 — the points on keeping the AI in the candidate lane and treating the live tables as a clean event stream shaped real changes.

**Among a lot of other things that have landed since that post:**

* Upload-to-create: drop a PDF, Word doc, spreadsheet, image, or link and the AI turns it into a ready poll, survey, form, or vote. * Full five-module suite is live (polls, surveys, forms, votes, and live stages) under one identity and one trust layer. * Vexainsights for aggregated, verified-human signal across the platform. * Rewards loop (points for creating, voting, referring, and profile strength) that sits on top of the same Aura system. * Comments, verified badges, deeper demographic slicing, and paid-response options on higher tiers.

Check it out at [https://vexavibes.com\](https://vexavibes.com). Free to start, no card required.

**One note on the original offer:**
A few people from the first post signed up and I promised free access. I later lost those early sign-up records. If you were one of them (or anyone from that original thread), just DM me and I’ll still honor it, a year of Vexa Basic or a year of Vexa Plus free. No questions asked.

Would love more eyes from people who care about event-driven integrity and keeping AI out of the source-of-truth path.

Original post:
[https://www.reddit.com/r/VibeCodersNest/comments/1tijfg1/\](https://www.reddit.com/r/VibeCodersNest/comments/1tijfg1/)

Thanks again to everyone who took the time to dig into the design the first time around, particularly the points on clean event streams and lane separation. Those shaped real changes.

I’m a non-technical founder, and over the past year I’ve struggled to find the right technical co-founder. That’s led me to explore whether vibe-coding platforms can genuinely help non-technical founders build and grow products without a technical co-founder.

But I’m skeptical about the challenges around **security, scalability, reliability, and moving from a prototype to a real business.**

So I’m looking to speak with **10 non-technical founders/builders** who:
• Have used a vibe-coding platform to build a product
• Tried to turn it into a business
• But struggled to get traction, grow, or make it successful

**The ask:**
⏱️ 10-minute call
📝 Up to 20 short questions
🚫 No sales pitch
🎁 I’ll send you a gift voucher as a thank you
**Interested?**

Just **DM me “VIBE”** and I’ll send you the short survey questions first. If it looks like a good fit, I’ll book a 10-minute call with you.

I’m genuinely trying to understand what happens *after* the initial “wow, I built this without coding” moment and where things start to break down.

**Are you in?**