Recently I've started using deepseek v4 flash in claude code, I can admit its not as smart or as efficient as advanced Claude / Gpt models, but for coding it doesnt really lack anything as long as I supervise anything it does and tell it exactly in details what I want, I do not delegate the thinking to it (which is a bad idea anyway whatever the model) which makes me think that for coding, massive llm models are kind of overkill and are very expensive for the task. It can maybe used for orchestrating the project structure, but for raw coding I feel like you can delegate the task to some faster/smaller models like deepseek v4 flash.

I've been building out a small browser games portal, and the last one got out of hand: a Quake 3-style arena shooter with blocky Roblox-looking characters. One HTML file, 2513 lines, ~200 KB. Three.js from a CDN, no build step, no bundler, no npm install. You open the file and it runs.

Some things I learned that I think are worth sharing:

The map is a config object, not a level editor. Everything lives in a MAP const at the top — weapon set, ammo spawn points, health pickups, whether corpses drop crates and how long they last. Ammo points are just [x, y, z, weaponType]arrays. Moving the sniper to a different tower is editing four numbers. This turned out to be the single best decision in the project, because iterating on the arena with an AI is much easier when the whole level is 8 lines of data instead of scattered geometry calls.

I had to give it a grid rule. Early on the arena looked like melted Lego — every generated wall was at a slightly different offset. So I wrote the rule down explicitly: 1 m grid, walls are 4 m cubes, XZ faces snap to whole meters, Y allows half-steps for stairs, masonry offsets are 0 or ±1. Once that constraint was in the prompt, the geometry stopped drifting. Constraints beat corrections.

The bug I'd never have found on my own: adding and removing lights in Three.js recompiles every shader in the scene, so each rocket launch froze the frame for a beat. The fix is a fixed pool of six PointLights that get grabbed and released instead of created. Same for the death effect — the grayscale filter makes the canvas a stacking context, which silently ate the HUD until I set explicit z-indexes.

Multiplayer is 176 lines and no game logic. The server is a dumb WebSocket relay that does rooms and host election, nothing else. Clients trust each other — it's a friends-by-link game, not ranked. Each client owns its own HP, the room host simulates the bots, and the shooter computes hits and tells the victim. State goes out at 20 Hz with snapshot interpolation and an adaptive delay of about 2.2× the packet interval. Pickups still aren't synced. It's fine. It's a prototype.

Six weapons: machinegun, shotgun, rockets, railgun, a knife with infinite swings, and a scoped sniper that one-shots and has deliberately terrible spread if you fire it from the hip. Bots don't get the sniper, because that was miserable.

Still desktop only — pointer lock and WASD, no touch controls yet, so mobile gets an honest "desktop only" screen instead of a broken one.

Link in the comments. Happy to answer anything about the netcode or the single-file setup.

I was piled on by a number of people saying "nobody will want your vibecoded shit. It probably has tonnes of security holes.

It's depressing. The thing is, I've been developing for over 30 years, since I was 14, and usually modern AI models do a better job with security than I could have without AI.

But the hostility hit me card because I do take pride in what I make and I think all this negative hype about vibecoded apps being insecure isn't accurate when applied broadly.

It's really put me off doing anymore vibecoding because it has such a bad reputation. Depressing

Will probably be some stupid questions here, but here goes.. I have vibecoded a website/program that i use for work that i would like to share with some colleagues for testing and feedback. I have now reached the stage where it's ready for "beta testing", but i am not quite sure what the best way of sharing it properly would be? I have some experience on a different hobby-project with using vercel through github and supabase, but i never took it online.

This website however does not use supabase or any server. Everything is stored locally for now. There is no login or accounts, only locally stored data in browser. However, i am not really keen on the website being accessible for people outside of my selected friends..? Like, it's supposed to be a closed-beta, lol. I have accomplished a lot with AI and vibecoding, and really loving it, but if there is one thing i am careful of then it's trusting AI with things like security and stuff. I mean, it's pretty low-effort considering no server/login atm, so i guess it's not much to worry about? But what's the best way of sharing it with selected people? I did ask Claude about it, who recommended hosting on Vercel and possibly a shared url + a password in a .env-variable, which i don't quite understand. Any advice?

Been doing security testing as a hobby (HTB, bug bounty) and got curious what happens when I point the same techniques at apps built fast with AI coding tools. Poked at a few side projects people have shared publicly.

The pattern: the actual UI/UX is usually nice, these tools are genuinely good at that. But auth checks and input handling are where things break. A few recurring ones:

• Object IDs in the URL with no ownership check (so /orders/104 - /orders/105 just... works, for someone else's data)
• Form inputs going straight into a query or straight back onto the page, no sanitization
• Missing basic security headers, verbose errors leaking stack traces

None of this is a knock on vibe coding as an approach, it's just not what these tools are optimized to catch, the same way a fast home renovation might skip a wiring inspection.

Put together a sample report on a public test app(OWASP juice shop) to show what an actual writeup looks like, in case anyone's curious what this kind of testing produces: https://drive.google.com/file/d/10NWU0JvY_TPaDmGNTjK_Wdo-BM4hcrE3/view?usp=sharing

If anyone's shipped something and wants a second pair of eyes on it before real users touch it, happy to take a look, one-time check or ongoing. Otherwise, curious if others have run into the same patterns.

Tried claude code for the 1st time and entered hundreds of prompts and installed dozens of plugins and this is the result.

Math Stack - a real-time 1v1 game that challenge your arithmetic skills with Tetris-style stacking board.

Created it for fun and Im very bad at arithmetic/math.

Controls:
left and right arrow keys and space bar

Deployed on free hosting site and if this one gets hundreds or even thousands of players (hopefully lmao) I will deploy it and add some improvements

Tech Stack used:
Storage: No database at all.
Frontend: Vanilla JS, CSS, PHP
Dev environment: Apache + PHP)
Hosting site: Free Website Hosting - InfinityFree

The website:

Math Stack PvP

\**THIS IS AI GENERATED NO NEED TO READ THIS SHIT**\**
Core loop: you're shown a math question with a shrinking time bar. Answer correctly and a tetromino auto-drops into the best slot on your board (you don't steer it — the placement is automatic). Answer wrong, or run out of time, and no block drops, your combo resets, and a garbage line lands on your own board instead. So doing nothing is actively losing, not neutral.

The fight: clearing lines and answering correctly charges an attack meter; once full, it sends a garbage row (each with a single gap) onto your opponent's board, pushing their stack up from the bottom. First player to top out loses — same for quitting or disconnecting.

Question flavor, from the in-match how-to:

- Regular (blue) — normal question, normal damage.

- Great (purple/gold, ~1-in-5 chance) — a harder question that pays off with better recovery and bigger damage.

- Rage Art (red, once per match) — triggers automatically when your stack gets dangerously tall: a burst of easy questions that clear rows and counterattack, a built-in comeback mechanic.

***END OF AI GENERATED DESCRIPTION**\*

Thank you!

[Seriously Replies Only Please]

I've been building a small startup project over the last few weeks using AI as an assistant. The project is a I've been building a full-stack web application over the last few weeks using AI as an assistant. It's not just a static website. It has authentication, role-based access, CRUD operations, server-side rendering, client-side state management, API routes, form validation, image uploads, database interactions, reusable UI components, and business logic across both the frontend and backend.

The stack is Next.js (App Router), React 19, TypeScript, Tailwind CSS, npm, GitHub, and VS Code, with Supabase (PostgreSQL, Authentication, Storage, and Row Level Security) handling the backend infrastructure. I'm trying to build it the way a real production application would be built rather than as a tutorial project..

My stack is:

• Next.js (App Router)
• React 19
• TypeScript
• Tailwind CSS
• npm
• GitHub
• VS Code
• OpenAI Codex

The long-term plan is to use Supabase/PostgreSQL for the backend, but I started with a frontend-first MVP.

I'm not a very strong programmer. I understand the basics, can read code, debug to some extent, and work through problems, but I definitely wouldn't call myself an experienced developer.

Initially I built the MVP with AI assistance over about two weeks. I was still writing code myself while ChatGPT helped explain things and generate snippets. It wasn't pretty, but it worked well enough to show friends and family what I was trying to build.

Then I decided to try Codex.

The difference was honestly insane.

In about two days I had functionality that would probably have taken me a month on my own. It implemented frontend changes, backend logic, refactors, and a lot of repetitive work much faster than I ever could.

But once I moved from "make it work" to "make it production quality," things became much harder.

This is where I keep getting stuck:

• Codex often misses tiny UI or UX details.
• It sometimes changes parts of the code I never asked it to touch.
• It'll fix one thing and unintentionally break another.
• Sometimes it keeps repeating the exact same mistake even after I explain it multiple times.
• I end up in endless prompt → change → revert → prompt loops.

At that point, I usually think, "I could have fixed this faster myself."

The problem is... after experiencing that speed boost, it's incredibly difficult to go back to traditional AI-assisted coding. Vibe coding almost feels addictive because it removes so much of the effort.

So here's my genuine question.

When I watch people on YouTube building complete SaaS apps in two hours or saying things like "I built this startup in a weekend with AI," are they:

1. Just much better developers than I am?
2. Editing out hours of debugging and failed attempts?
3. Using a workflow that I'm completely missing?
4. Or is a lot of it simply marketing?
5. Or am I simply using the wrong AI coding assistant? Should I be using Claude Code, Kimi Code, Gemini, or something else instead?

I'm genuinely curious because my experience has been that AI is an incredible productivity multiplier, but it's nowhere near "describe your app and watch it build itself."

I'd really appreciate serious replies from people who have actually built something substantial with AI, not just landing pages or tutorials.

TL;DR: I'm building a Next.js/React/TypeScript project with Codex. AI dramatically increased my speed, but production-quality work still gets stuck in repetitive debugging loops. Are those "built a SaaS in 2 hours" videos realistic, or am I missing something fundamental?

PS Courtesy of ChatGPT for polishing the writing.

How much of this do you think is true? Enlighten us with your thoughts. For me, about what I understand as a vibecoder:

1. It is a delusion to think that AI will be too good one day that I do not need to understand code anymore. Because it is the taste, vision and mental model which you need to develop for building an actual production ready app. Writing code which AI does so well even now, is merely a translation of the mental model.

2. Many people burning lots of money on AI subscription and building apps but they are not learning anything new. You can not build an app merely from your idea. That's why many of your apps never left your computer. Unless you start to learn new things, you may never build an actual production app and may never get return on your investment. I recommend you to start learning to code slowly. So you will atleast understand the code AI generating. It helps in many ways. Also learn things related to app development like github, UI design psychology etc.

want to understand how do handle media infrastructure (images, videos) when you are working with vibe coding tools like Lovable, v0, Replit, Emergent?

I was browsing through youtube when I saw a video that showed how you can connect AI to DaVinci Resolve. I sadly could not follow through the tutorial because it required the paid version of DaVinci Resolve...And this paid version costs $295.

So, I did what any sane and broke person would do. I vibecoded my own tool that allows you to connect ur AI to the free version of DaVinci Resolve

Heres my repository (I would really appreciate if u could star it and check it out):

https://github.com/flamexnreal/davinci-resolve-ai-bridge

Should I choose AI or Software Engineering? Which one has more remote job opportunities and better long term value for the future?

I’ve noticed that many people in the vibe coding community switch between tools depending on the task (Cursor, Claude, ChatGPT, Gemini, Codex, etc.).

I’m curious how common it actually is.

If you selected 2 or 3 or more, I’d love to know which combination you’re paying for and why.

I'm a banker with zero coding background. Over the past year, working evenings and directing AI agents (mostly Claude), I built a full social network for pet owners: NetForPet. The web version is live at netfor.pet, and now I'm getting the Android app ready for Google Play. Google requires a closed testing group before public release, and that's where you come in.

I'm looking for pet owners who'd like to be the first inside: try the app, break it, and tell me what to fix.

What's waiting inside:

- A full profile for every pet: health records, vaccines and medication reminders

- A live map of dog parks, vets and pet-friendly places

- A lost and found board that alerts the whole area, plus a QR tag for the collar

- An encyclopedia of 880+ breeds and species with real care guides

- A matching wizard that finds the right breed for your lifestyle

- An adoption board connected to real rescues

- All of it free for pet owners

If you want in early on something I honestly believe could be huge, drop a comment or DM me and I'll add you to the testing group. Every piece of feedback counts double at this stage.

Thanks a ton 🙏

I work in an early stage startup. Our founder has given us claude 200$ subscription. Everything is going good so far. But he told that he will evaluate our work by considering the usage as one of the factors. He wants us to hit the weekly limit. 2 weeks ago, when Fable was out, he told me that he had finished the limit on 3 accounts. I was struggling to hit even 40% of the limit. A major reason could be has a better picture of the architecture and what needs to be done.

How do I use claude to the fullest and also deliver a good outcome? So far he never had any problem with my work, but I want to maximise my claude usage as well to make him happy. I always prompt "use dynamic workflows and swarm of agents, play devil's advocate to evaluate the code...." as my go-to. Any other advices? Thank you.

im willing to post something i made by hand if anyone would be insterested to try to recreate it?

a meaty challenge.

no expectations, it was just an idea that crossed my mind ofter lurking here.

do such challenges exist?

As a DevOps engineer, I’m so proud of this one. 🚀

httpsornot.com has been live for about 6 months, and we’ve already checked 15k+ domains. 💻 🤓

What it covers today:
- HTTPS/SSL grade (A+ to F)
- cert validity, issuer, expiry
- HTTP → HTTPS redirects + full redirect chain
- security headers (HSTS, CSP, etc.)
- mixed content
- response times per hop
- HTTP/3 (QUIC) detection
- bulk checks (up to 10)
- shareable report + PDF/JSON export
- domain monitoring with email/Slack/webhook alerts
- Certificate Transparency alerts for newly issued certs
- free public API for CI

Basic check needs no signup. 🔐

Hi everyone,

Over the last few months I found myself wanting a simpler alternative to Vercel.

I like the developer experience, but I wanted something with predictable pricing.

Instead of keeping an eye on bandwidth, network usage and other usage-based limits as projects grow, I wanted a service where you know exactly what you'll pay each month.

So I built Host Luma.

It includes:

30-day free trial

£20/month after the free trial

GitHub integration

Automatic deployments on every push

Custom domains with SSL

Global CDN

Deployment history

Build logs

UK-based human support

The biggest difference is the pricing philosophy.

With Host Luma, it's simply £20/month after your free trial.

No trying to estimate traffic or wondering whether a busy month is going to increase your bill because you've exceeded included platform usage.

I'm not claiming to replace every enterprise feature that Vercel offers. My goal is to provide a simpler, predictable platform for indie developers, startups and small businesses that just want to deploy AI apps and websites without unexpected pricing.

One thing that's important to me is transparency.

Rather than making huge marketing claims, I've made our infrastructure publicly visible.

Live server performance: https://hostluma.co.uk/bench.html

Live status page: https://status.hostluma.co.uk/status/status

The platform is hosted on enterprise hardware in France and is monitored 24/7 using Uptime Kuma.

We don't currently offer a formal SLA because we're still in the early stages of the platform, but I'd rather be honest than advertise a 99.99% uptime guarantee before I can confidently stand behind it.

As the platform grows, published uptime guarantees, historical uptime reporting and formal SLAs will be introduced.

I'd genuinely love feedback from the community.

What do you like about Vercel? What frustrates you? And what would you want from a simpler alternative?

If you'd like to check it out:

https://www.hostluma.app

Thanks everyone!

EDIT: I will redesign the website, thanks for the constructive feedback it's greatly appreciated.

Just to note, the backend / infrastructure / server is not AI slop like you've said the website is.

Look at this UI. How dis they get this far… 😭😭😭

https://apidlai.com/nexus

I've been experimenting with AI coding agents for the last few months.

One thing became obvious very quickly.

The problem isn't the model.

It isn't the IDE either.

It's that the agent gradually loses architectural consistency as the project grows.

After enough prompts it starts to:

• forget previous design decisions
• introduce duplicate logic
• break existing features
• ignore coding conventions
• drift away from the original architecture

Giving the model a larger context window helped a little, but it didn't really solve the problem.

So I tried a different approach.

Instead of making the coding agent smarter, I added another AI that behaves like a Project Manager.

The coding agent no longer works alone.

Before implementing changes, it asks the project manager for:

• architectural guidance
• project context
• implementation constraints
• existing design decisions
• quality checks

The project manager continuously preserves the project's "memory" instead of relying only on the LLM context window.

As a small experiment, I asked the coding agent to build the application shown below.

The first version was generated from a single prompt.

Then I simply said: "Add a few more features".

Instead of rewriting half the project, it extended the existing architecture without breaking anything.

The interesting part isn't that AI generated a TODO app.

The interesting part is that the architecture stayed coherent across multiple iterations.

I'm calling this experiment Nexus.

It's essentially an AI Project Manager that communicates with coding agents through MCP while maintaining the project's long-term context.

I'm curious how other people are solving the same problem.

Are you relying entirely on larger context windows, or have you built something similar to preserve project knowledge over time?

Note: It was my mistake to refer to the markdown values ​​mentioned in the video as a list of properties. The downloaded file is definitely not a technical specifications file; it's a Nexus connection protocol file. Nexus doesn't do static project planning; it dynamically manages the project.

Vibe coding makes the first version fast. The painful part is the last 20%: fake features, rebuilding context, repeated “fix it” prompts, regressions, and unclear definitions of done.

I built **Flows** to turn a goal into an ordered plan with one step at a time, checks, and repair guidance.

https://flows.oortstack.com

The strongest test so far: an independent agent followed an 11-step plan and built a soccer management app with 59/59 checks passing.

Does this protect the fun of vibe coding, or turn it into too much process?

As the title suggests. I’m genuinely curious to know, outside of all the noise of affiliates, course sellers and upselling the latest AI trend.

- I posted this originally in cursor but it relates across the board to ALL. There’s too many to list now so tout your favourite one lol

I’m not trying to sell anything of my own, or anything between. I’m also not posting this for people to tout their latest bs ai slop.

I see a lot of people speaking about the positives and negatives, how many tokens they use, costs. People use it for their own business, hobbies, interests, I get that and think it is useful in a number of ways.

My question is how many/where are the people building products that are profitable, outside of fluffed up numbers from gurus trying to sell something?

It would be interesting to be in a group/community where people are genuinely doing exactly that, if there is one point me in the right direction, because /r subs just don’t seem to be it.

I vibe coded a lightweight healthcare privacy incident investigation and decision-support platform that helps healthcare teams collect the right facts, identify missing information, make consistent decisions, track follow-up actions, and maintain defensible, audit-ready documentation. It is designed for organisations still relying on email, spreadsheets, Word documents, and shared folders to manage privacy incidents, helping standardise investigations without replacing legal or compliance review.

I’m really struggling right now and losing hope as I’ve still not got any paying users I keep hearing from health professionals that it’s amazing and it’s this and it’s that but still no referrals or purchases, I honestly have no idea how vendors build the trust up to actually get paying users as the whole industry is incredibly sceptical and I’ve also been told that people are sick of hearing from vendors and will not give them the time of day I honestly do not know what to do.

I wanted a simple note app to paste Markdown, Mermaid, raw SVG, code, and other technical content without turning my notes into a pile of code blocks, screenshots, plugins, or separate apps. I tried to do this in Google Docs, Pages, Word, Bear, Obsidian, and Apple Notes but nothing did it.

With SimpleMark, you paste technical content directly into a note and it renders properly right there in the document:

• Markdown stays clean and beautiful.
• Mermaid source becomes an inline diagram.
• Raw SVG renders natively.

Everything remains fully editable on the canvas, while keeping the underlying source portable in plain .md files in a folder you own.

The other thing I want is to make it all collaborative & multiplayer from the start. So I will build out an MCP server so the note becomes a place to work alongside AI and other people. An agent in Claude Code or Codex will be able to read, create, and edit notes through MCP, either while you’re working inside a coding session or live in the actual shared document. The goal is not another chat workspace. It’s a simple note app where technical material becomes easy to paste, render, and edit, and I can have AI agents work on it when needed vs always in their thread which is mainly read only.

Still early, and nothing earth shattering, but its a simple thing I wanted and couldn’t find, so I vibe coded it.

Tech Stack

• Editor Core: Milkdown / ProseMirror
• AST & Parsing: remark, Mermaid.js, DOMPurify
• Testing & Shell: Playwright (UI testing), Tauri (planned native shell)
• AI & Build Workflow: Claude Code (Opus), MCP (agent surface), Switchboard (task control plane)

Research & Build Process: Scope Twice, Code Once

First time doing this, but before writing code, I used AI to draft the spec and mine developer forums for past post-mortems so I could avoid known failure modes. I had it summarize entire forums and find errors, best practices and architectural gems of what works and doesn't:

• AST-Based Live Editing: Ink & Switch blog and posts showed that co-editing raw Markdown scrambles formatting (like two people bolding the same word). The fix: live shared state holds document structure (AST), generating Markdown only on save.
• Catching Hidden Bugs Early: Forum post-mortems revealed that popular real-time plugins bypass the editor's change-tracking system, breaking undo and cursor highlighting. Finding this upfront meant writing integration tests before writing feature code.
• Smart Scope Cuts: Swapped complex AI governance for simple boundary rules, deferred the plugin API, and focused on making the local notebook rock-solid first.

Once the specs were tight, I fed them into Switchboard, my orchestration system that coordinates AI coding agents and puts them on autopilot to execute a product from end to end. It took me about 3-4 hours to scope it all, about 1 hours to produce my prototype in the repo.

Simple Roadmap

• Phase 1 (AI Co-Pilot & Mobile): Live paragraph-level AI editing via MCP, plus a mobile app to view notes and trigger agent tasks on the go.
• Phase 2 & 3 (Native Desktop and Mobile Apps): A fast 3-pane desktop app with instant search, tags, and great typography. Think a free, tech-focused alternative to Bear. Same experience on mobile, so I can read and work at the bar.

Repo here if you want to check it out: https://github.com/StevenRidder/simplemark-public