Vibecoding
Build for the vibe, debug later
Start new thread

non-engineer here. the thing i vibe code most is throwaway html

by•

disclaimer: I'm not an engineer. i do growth and marketing.

when people talk about vibe coding they usually mean shipping a product. an app, a saas, a tool with real users. that's the version that gets posted. but it's not where things actually changed for me.

my shift was smaller and kind of weird: I started using AI to generate HTML for stuff i'd never have bothered building before.

  • a daily report i was sick of reformatting

  • a dashboard for one set of ad numbers

  • a calculator for some unit economics i needed once and then never again.

none of these are products. half of them i used once and closed the tab. but a year ago every single one would've been a messy spreadsheet, an ugly slide, or a thing i asked an engineer for and felt slightly bad about.

now i just describe what i want and get something that looks good and works. (of course the prompting method is important too if you want to control the output as close to what you expected)

the part that got me is it crept into the real work too. I write client proposals as HTML now 🤣. I hand my engineers architecture docs as html. and they actually read them, which a 200 line doc never managed.

so here's where i've landed: Vibe coding's quiet win for non-engineers isn't "anyone can build an app." it's that building something small and disposable stopped costing anything. the floor just dropped.

curious where everyone else is at?

what's the most useful thing you've vibe coded that wasn't a product?

51 views

Add a comment

Replies

Best

As a developer, I'm using AI quite often for building one-time scripts that I'll never need again (most likely), but which are doing some dirty job for me (exactly as you described). This is a major win!

 yeah this is the part i find interesting

btw what's the dirtiest one-off you've handed off lately? ( ꩜ ᯅ ꩜;) 

 hmm, I'm usually not handing them off, just using them by myself :) And to be honest, I cannot even recall, because that's not something that is happening often enough in order to keep them in my memory

This hits perfectly, Nathan — and honestly, you described exactly my journey.

I'm not a developer either. I'm an electrician by trade. A year ago, the idea of building anything interactive felt completely out of reach for me.

Then I started using Replit Agent — and everything shifted. I built things I never thought I could: a diagnostic tool for electrical installations, interactive checklists, calculation sheets that actually look good. Not products. Just useful, disposable things that saved me real time on real jobs.

But what really changed my workflow is what I built on top of that — NEXIA, an AI assistant that generates structured HTML directly from a conversation. No prompt engineering, no IDE. You describe what you need, it outputs:

- Interactive simulations (fluid flow, electrical circuits, pendulums)

- Financial dashboards and business plan projections

- 3D viewers for mechanical parts

- Full technical reports and calculation notes

- Personality tests and interactive forms

All as standalone .html files. Open in browser. Done.

Your "throwaway HTML" framing is exactly right. The floor just dropped — and most people haven't noticed yet.

Launching June 17th if you want to see it in action

 wow I have never thought that Replit have that capability. But agree with you that applying AI to your domain knowledge making you more powerful than peer. this is a bold statement lol

also, can you share me the work of that HTML file? Do you know where to host it?

Hey Nathan! Thanks for asking 🙏 The HTML files NEXIA generates are completely standalone — no hosting needed. You just open them in your browser, that's it. Here's what I mean. From a single conversation, NEXIA can output: - An interactive electrical diagnostic tool (my actual use case as an electrician) - A fluid flow or circuit simulation — fully animated, no library - A financial dashboard with real calculations - A 3D viewer for mechanical parts — rotatable in browser - A personality test with radar chart and personalized results All as a single .html file. No server. No npm. No deployment. Just open it. That's the part that changed everything for me — I'm not maintaining anything. I describe what I need, NEXIA builds it, I use it, done. If you want to see it live → orion-tek . io/beta (launching June 17th 🚀) By the way — do you have an email where I can send you a few of these HTML files directly? Would love to show you some concrete examples 🙏

All of my projects started out not as products - but as things I needed at the time. An app to create HTML pages. A transcription tool I didn't need a subscription for. A way to turn custom GPTs into standalone AI apps.

Some have grown into tools with paying customers, and now I go product-first in general but this is how I started out too.

 ha, you said the magic words. same story as you

for instant, uselink started because i do growth, generate a pile of html in claude, and every file died the second someone needed to read it.

so we built it for ourselves first, turns out everyone generating with AI has the same problem.

I relate to this. For me, the useful part is not always building a product but making small things that remove friction from daily work. A quick HTML report or a cleaner client proposal can be enough. It makes the idea easier to share and you don't have to wait for someone else to build it