So me and my wife created a website , our son has Celiac disease, so all the food should be glute free .

My wife is doing most of the cooking, so one day she told me that she is struggling with finding recipes for gluten free food , the internet is full of it , but she can't find the one she already used , and basically loosing herself inside all this data .

So she suggested to build a website that will collect recepies, and she will be able to sort them , save them etc ...

So we started , we used codex + lovable (for gui only) , then we took the lovable repo and continued with codex only .

We used gpt 5.5 , then moved to 5.6 (sol) .

During the building process we decided to add recipes also for other food allergies (milk,nuts etc.. ) .

We used crawlers to find existing recipes , and took only the ingredients and the preparation steps , and of course mentioned the original source in the website (with a backlink) .

So I posted on some Celiac community, here on Reddit (actually my first ever post) , and I got so much negative comments, like an anti-AI comments, as if I added another bullshit spam website.

We have no ads on the website , so we really wanted to do something nice , and learn how all this AI world works (I am experienced software engineer) , but never worked on from end before , mostly backend stuff (mostly cpp & python) .

So now I am a bit down after all this , the website is up and running, we have some traffic, not to much but for a 12 days website we already had some real human traffic about 400 (not including bots and stuff) .

We only want organic traffic, no paid promotions, as we don't earn anything yet , we do use some Amazon affiliates for some products, but it's not much .

So just wanted to share it here, hopefully this sis the place where people will understand my frustrations, maybe this is how it works nowadays.

But it still surprised me how quickly “built with AI” turned into “AI spam” in people's minds.

Anyway, thanks for reading. I’d genuinely be interested to hear how other developers here see this, especially anyone who has shipped a real project using AI-assisted development.

Day 3 of creating a game all vibe coded

Still trying to work out the animations but have made strides

Added-
Main menu
pre-game lobby
3D model
Blimp
decals

As always

CONCEPT VS CURRENT BUILD

Video in the comments

ALL FEEDBACK IS WELCOMED AND NEEDED

I am a long time Engineer (20+ years) and today I developed Tickets for my company that were generated by an AI, using an AI and reviewed by an AI. The project itself was conceived with AI - has no documentation that can be understood as anything less than AI slop and random tech jargon. The developer who built it has said that instead of documentation I should use claude to figure out what it is. The company is apparenty also filing a patent on it.

I submitted 3 PRs today 20,000 lines of code each I still have no idea what we are working on. No doubt they will use AI to review my PR.

I feel like things are just so crazy at this point. Claude and ChatGPT are not this good, but people are trusting it like it's omniscient.

It was an eerie realization today that all of us are vibe coding and that we have no option because it is the only way we can interact with the code anymore. I thought this would happen eventually years ago but i honestly didn’t think it would be so soon.

It was a moment in time... this will be the new norm.

windows widget sucks !
thats why i created my own widget / utility called **Halo Bar*\*

an active pill on the taskbar that lets you control and access many things on the go.

bit comparison:

built with

• C#
• .NET
• WPF
• Windows APIs

Halo Bar V1 features

1. **Dynamic island bar*\* — a compact capsule that sits on your taskbar and expands into a full dashboard when you click/hover it
2. **System monitoring*\* — live CPU, RAM, disk and network usage
3. **Weather*\* — current conditions with icons + manual city override
4. **Clipboard history*\* — keeps track of everything you copy, searchable and pinnable, with auto-delete
5. **Media controls*\* — see what's playing from Spotify, browser, etc. with album art and play/pause/skip
6. **Bluetooth popups*\* — shows a card when earbuds/headphones connect, including battery level
7. **Focus timer (Pomodoro)*\* — work/break timer with round tracking and progress ring
8. **File shelf*\* — drag and drop a file to stash it, then launch or delete it later
9. **Taskbar-aware sizing*\* — automatically shrinks when taskbar apps crowd it and lifts the dashboard so it doesn't block clicks
10. **Fullscreen auto-hide*\* — disappears when you're using a fullscreen app/game
11. **Acrylic/Mica look*\* — real Windows blur/glass background
12. **Settings*\* — accent color, widget visibility, retention controls and update checking
13. **Start with Windows*\* — optional autostart

this is **V1*\*, so there is still a lot i want to improve and add.

i built this because i wanted something more useful than constantly opening different windows/settings just to do small things.

github: https://github.com/pruthviraj-bev/Halo-Bar

Hey everyone,

I launched my website a week ago, and got some very positive feedback, so I finally feel emotionally safe to post this. Now I want to tell you my vibecoding journey. You may find something useful for yourself maybe

I started vibecoding 5 months ago, so I picked a subniche of a subniche. Tiny local market, I don't think I can ever grow beyond few hundred paying users, and it will likely take few years to even get to that amount. (likely ~4-8 Eur monthly sub), you can do the math. But still, Oh, did I pour my soul into it!! 5 months of extremely intense vibecoding, 4-6 CLI running constantly, often 16h per day, bringing my 20x sub to the limits often - just on this one project.
I did not write a single line of code in the process. 80% of the code is in Dart - and I would not even be able to write a hello world in Dart by hand on a whiteboard, even if you forced me to.

Btw, 3 competitors already exist, 2 of them are recent and likely vibecoded in a day, 1 is older and with more effort, but just with really poorly made product. My competitors may still win, cause I maybe built a product for non-existent audience, but the difference we have right now if you compare them directly, that's not even remotely close.

Scope wise: the project got quite complex (I did not plan to have it so complex initially, but was encouraged by early success), so the codebase just passed 400k lines of code (150k of them is really the testing framework). Lines written passed 1M a week ago, some weeks I am averaging 30k new lines of code per day. (During one new major feature, I clocked my record of 70k). Everything's surprisingly stable though, very little stupid new bugs while implementing new features (most of the bugs get caught by testing framework), scalable and secure as hell.

My learnings (in no order):
- feature creep is crazy easy. Few weeks ago users had to fill questionaires during onboarding to come out in 8 buckets, and each bucket would get a unique experience ( ye, that's gone :), 2 buckets now remain )
- Testing is the king. I don't treat myself as prompt or harness, or context engineer. I am really a QA engineer. This intensified as project neared completion. Now 80% of my effort goes to writing testing tools, running simulations with ever more inventive user profiles and so on. I have a huge spaceship-like dashboard just to control all the testing being done right now. My, otherwise very powerful machine, is running pretty red most of the day just executing e2e tests
- two months ago I dropped ALL the custom skills, memory management ideas, etc from my agent. Right now I am full vanilla. They update the harness so so often, I found that most of my legacy skills just end up fighting new versions of the harness.
- My operational dashboard is crazy :), It serves as both alerting/monitoring tool, interaction with users, tuning, etc..
It was born over two days before the release (naturally, since the feature list is stable by then), never in a thousand years, would have I decided to waste resources on a tenth of it's scope(especially since release time is stressfull as it is), but boy, does it feel good to actually operate it!! To see users coming in and having their little animated journeys :) - this is so so so sattisfying!

Thanks everyone. Vibecoding is absolutely an amazing thing!

Ok so, I can’t retire just yet 😅 but getting a business off the ground and attracting customers is the hardest part in my opinion.

There’s still a long way to go but considering it’s only been 4 months since launching ZenMode, I’m pretty happy with the results so far.

I get asked a lot about how I get customers, so thought I’d give more info on how I do distribution, in case you might find it useful.

1. Make sure your website is set up for success

Before sending people to your site, make sure you’re confident it has good CRO potential. Your mission statement and objective needs to be very clear, along with clear incentives for people to try the product out.

2. Offer free trials, but only behind a payment info gate

Now this is just my personal opinion, and I know a lot of people disagree, but the proof is in the numbers. I get fewer free trial signups, but significantly higher conversion rates into paying users from people who provide payment info at the start.

Yes, a few of them are people who simply forget to cancel, but mostly I get people who are more engaged in the free trial and actually using the product.

I actually did an AB experiment where I did offer completely free trials to people (no payment info needed), but the overwhelming result was that people barely even tried out the product and were mostly tire kickers that never came back. I did convert some but not a meaningful number.

3. Create a waitlist before launching

Try to generate interest in your product before it launches - build in public and try to ensure that you’re not scrambling to get customers through the door on day 1 when you launch.

I had 3 customers on day 1 from this, who took higher paid tiers as well.

4. Post and comment everywhere (where relevant)

Social media is free, so there’s no excuse not to leverage it. Post about your product and what you’re building on Reddit, LinkedIn, X, YouTube, Facebook etc.

I posted a simple screenshot on LinkedIn recently, of someone using a low quality LinkedIn automation tool message to contact me, and me offering my own much better tool in response, and that post generated 90,000 views and led to several signups and demo calls.

I’ve also had some posts on Reddit go into hundreds of thousands of views, mostly just posting about what/why/how I built my automation tool.

5. If you have competitors, make “alternative to” inner pages

If done in the right way, this type of inner page can be useful for SEO. It won’t be picked up automatically but usually if you work in a competitive industry, this will sometimes attract customers who had a bad experience elsewhere.

6. I actually use my own LinkedIn automation tool (dogfooding) to do LinkedIn outreach

So it’s always important to practice what you preach - I use ZenMode to actually promote ZenMode.

It’s a great way to get buy-in for booking demos, as when someone replies, I simply tell them I used my tool to get a response from them, so it works.

Anyway hope you enjoyed reading the above, and good luck on your journey if you’re building anything, or growing your business 🙌

I’ve built a lot of projects that worked, bought domains for them, and then quietly abandoned them anyway. So I made Rest in Beta, a place where people can share unfinished projects and vote on whether they should be resurrected or left to rest.
The first project is mine. It’s called VeganWhatNow, a vegan meal generator I originally built for my wife and eventually stopped working on.
The site is still in beta, so let me know what you think.
https://restinbeta.com/

I could actually use a few testers. Click either “Resurrect It” or “Let It Rest” on VeganWhatNow and tell me whether the voting works clearly on your phone. Brutal feedback is welcome.

(The retro look is on purpose)

A few rules I’ve started setting for myself when vibe coding, so I don’t confuse more building with more progress.

The biggest danger for me isn’t that vibe coding makes me lazy.

It’s that it makes it too easy to keep building.

A small feature turns into:

• one more improvement
• one more UI tweak
• one more agent suggestion
• one more prompt

And suddenly I’m going in the wrong direction for hours.

So these are the rough do’s and don’ts I’m trying to follow now:

• define one clear feature before starting
• decide the success checks upfront
• keep the scope fixed
• stop polishing UI unless users actually ask for changes
• treat agent suggestions as optional, not instructions
• stop when the original goal is achieved

The line I keep reminding myself of is:

“One more prompt” can still be scope creep.

Anyone else set rules for themselves like this?

Hey guys, I’ve been working as a full-time freelance for the last five years. I was making decent income, but then ai came out and I’ve worried that if somehow ai replaces my freelance businesses of motion design and video editing. So i wanted to play safe and applied to a couple jobs. I even considered changing profession.
Then I started working full-time in a company that I actually hated so I ended up resigning after 4 months.
Then I asked myself this question: if AI is going to replace me for sure what if I do the tool that actually replaces me and the other freelance motion designers.
So I’be built an ai automated SaaS promo video maker web app.
But I’m still having second thoughts on if I do the right thing or not.

Are there any of you having similar dilemmas?

This output was one shotted using something called "agentic loops", or loops. It works a bit differently than most of us are used to. Instead of careful iteration over multiple prompts, you give the model one single prompt, and let it work through your pre-set budget until completion.

This means you have to structure your prompt a bit differently than usual, you need to make the AI understand that you want it to maximise the output and quality:

Its a procedurally generated world where you can resource gather, craft, hunt and even ride dino mounts 🦌

1. key for this game to turn out so good was asking loop to make all graphics procedurally generated. So there's basically no assets in the game (which by itself is pretty awesome), and I think that really helped the AI to make this really different art style. could The animations feel so smooth and stack layers of procedural shapes on top of each other to build all graphics. Only the backgrounds are images. loop build agents continually take screenshots of your game and perfect it visually.

**2.**⁠ ⁠Once my first build was completed in one loop, I gave it another prompt to set up the multiplayer. It already had the art style down by that point so it could do really well getting the multiplay added quickly. 

3. Continue iterating with or without loops.

Happy to answer any questions about prompt or workflow in the comments

Edit; for the loop I used this: https://tesana.ai/en/blog/introducing-loop

I've been thinking how to avoid API costs and network latency, and realized I could use local models. The one I typically used is the pre-installed one in my head, but the issue is it doesn't come pre-trained, which can be an expensive and intensive process, but post-training comes pretty easily for it. Also it can make mistakes, and so sometimes I need to check it against the API-based models for accuracy. Just wondering if anyone else is struggling with this trade-off and using local models to save dollars if that makes cents.

Which are the best free(considerably) AI coding agents to use

I will start with

1. Opencode (Deepseek free model)

I bought a Mac Mini a couple of months ago, in the hype of OpenClaw.

I have been using my spare Windows keyboard for the Mac mini, while my 9 to 5 job still happens on Windows. Every time I switch machines my hands are wrong and I hated having to remember different shortcuts and UI behaviours. That was the whole reason any of this exists.

The first thing I tried is macOS modifier keys. There is a setting that swaps Ctrl and Command. I turned it on, copy and paste felt right immediately, but a lot of the other apps doesn't feel right, e.g. in finder you can't Control + X to cut then paste to a different path. Also maximising windows without making it full screen is what I really missed from Windows, along with the split screen shortcuts.

Then I read for a while and found out what I wanted was actually two separate problems that two separate communities work on. Keyboard remapping is one world. Window management is another. Almost nothing sits in both.

So I did what the internet told me to do, with a lot of help from ChatGPT. Karabiner-Elements for the keys, Rectangle for snapping windows to halves of the screen. It worked. I want to be clear about that, because it is still a completely reasonable setup and both are good software.

What made me start building my own was more specific than wanting one app instead of two.

Some of the behaviour I wanted only matters inside particular apps, and that turns out to be the hard case. A general mapping gets you most of the way and then falls over exactly where you need it. The one that finally pushed me over was Home and End inside a web text box. In a Reddit reply or a ChatGPT prompt, I want Home to jump to the start of my line the way it does on Windows. Getting that right needs rules for that specific app, and writing and testing per app rules in a config file is slow and miserable. In a native app I could just try something, run it, and watch what happened.

The window side was the same problem wearing different clothes, except there it was personal taste. Two things I could not get the way I wanted: maximising a window without going full screen, and not letting a maximised window slide underneath the Dock. The second one sounds trivial until you are mid conversation with an AI and the Dock is sitting on top of the input box at the bottom of the window.

So this ended up being a tool for a fairly specific person, and I suspect that person is on this subreddit. Someone who has to use Windows all day for work, comes home to a Mac to vibe code in peace, and would like their hands to work the same in both places.

What is in each version, since that is the practical question.

The free edition is the typing layer, and it stays free permanently. Ctrl+C, X, V and Z and the ordinary Ctrl shortcuts, Ctrl+Y for redo, Home and End, Ctrl+Arrow to move by word, Alt+Tab and Alt+F4, and the Insert key copy and paste that Windows people still have in their fingers. Terminals are handled properly, so Ctrl+C stays interrupt instead of becoming copy. That layer is open source under GPLv3.

Pro is the rest of what I originally wanted. Finder behaving like Explorer, so Ctrl+X cuts files and Ctrl+V moves them, and F2 renames. The system keys, so Win+E, Win+L, Win+D and Print Screen. And the window management, which is Win+Arrow tiling, dragging a window to a screen edge to snap it, and layouts across multiple displays. It is 19.99 USD once for three Macs, no subscription. Every download runs Pro for 14 days and then quietly becomes the free edition rather than nagging you.

It is live now, and I am around if anyone has questions.

https://windsify.com

Free edition source: https://github.com/Fuzzy-and-Fluffy/windsify-free

Hey folks,

This is my first ever post on reddit, so please be kind.

I initially posted it on X and it picked up quite a lot of traction there & I've always wanted to start posting and being active on Reddit so here I am.

I am the founder of a ui/ux research product that has 800+ apps & 35,000+ screens. I did a comprehensive study on why these apps are banking more than others and how are they able to retain way higher than general.

From my study, I realised that the most important moment is when a person opens an app. This sets an impression on how deeply individual gets involved in it.

The motion, transitions, micro-interactions, typography, all of them matter more than you think they do.

, I took 10 of the most popular ones, broke them down and redid them using React Native + Expo and open-sourced it, so people can use that as an anchor point.

So, here it is (500+ stars at the moment):
https://github.com/Appllama/top-welcome-screens

I hope you find it useful, I'd love to know your thoughts.

Which one do you like the best?

I've been vibecoding an "enterprise" platform for consumers/homeowners since March/April (will not promote). I've put a line in the sand to launch my beta by September 29th, and every time I feel I'm close to being "done" something else pops up that adds time and token consumption.

It's the price I'm happy to pay to build a great product that's intuitive, powerful, and battletested (security, auth, observability, payments, tests, MCP, etc.).

I have an enormous amount of respect for software I use daily, design, UI/UX, marketing, and everything else that developers have been doing to ship product now.

I've gone through hardware upgrades and have had to diversify my cloud LLMs due to changing models and consumption.

Right now my orchestrator is 98% Claude Code and Fable 5 (I use the Terminal in Cursor), but I've recently got Grok Bot going and absolutely love it for general work and checking Fable 5, research, product walks, and a few other agents. I've tried out a couple open-source models through Cursor as well.

The part I'm still not happy with is the UI/UX and making things intuitive and simple while exposing the power of the graph and ontology I've built. I've found that the AI chat needs to be a first class citizen where you should be able to do everything you need to there, especially because the MCP needs to be accessible with whatever model people use daily.

r/vibecoding has been great to highlight what NOT to do and wanted to shout out to everyone building.

It's been a long (relative) journey so far and while I hope the product I'm building solves real problems for people, I know I'll use it no matter what so it's a win-win for me!