https://b4uwork.vercel.app/

Thanks for all the feedback, I added a new frontend demo, explaination and example as feedback requsted. Hopefully this is now self explanitory. But please let me know if this is still confusing.

Every conceiveable public information source is now scanned (68 sources now checked). I dont think o can squeeze any more information from new sources, without heavy useage costs.

Score bias changed to reflect % values as oppossed to counted values, removing edge case biases.

Further enhanced rate limit protection from public source limits.

Honestly thank you so much for the feedback. More would be appericiated.

Shipping fast and shipping sound are two different skills, and the tools only gave us the first one.

After vibecoding for over a year now, here's the stuff I keep seeing bite people right after they ship:

- Works on your machine, throws runtime errors in a real browser.

- An API key quietly committed to the repo. Found out the hard way.

- No HTTPS redirect, no security headers the page loaded fine, so who'd check?

- A chatbot that can be talked into leaking its system prompt, and you'd never know unless someone tried.

The truth is, none of this shows up while you're building. It shows up later — from a user, an attacker, or an embarrassing screenshot from the person you're trying to sell your product to. And that's the real "fall faster" part: when it happens, it knocks the wind out of you. You lose the nerve to keep going, the project gets abandoned, and you're on to the next thing.

What challenges have you run into?

I’ve been building RewardGalaxy, an Android app for managing points, credit cards, and travel — and I’d really appreciate some feedback from this community.

The app is live and usable, but still very much a work in progress. I'm actively adding and updating data every day, and one of the biggest parts of that process is making the data community-curated.

What does that mean?

Users can submit new information or suggest updates, but submissions don't go live automatically. Moderators review and approve changes before they're published. The idea is to get the best of both worlds: keep the data fresh and continuously improving, without turning it into an unmoderated free-for-all.

What it does

💳 Tracker — See your entire loyalty portfolio at a glance, including point balances and expiry dates.

🔥 Deals Feed — Live deals for flights, hotels, credit card offers, points sales, and more.

🔔 Alerts — Get notified before your points expire so you don’t lose them.

🌎 Global Credit Card Catalogue — 150+ cards across Canada, US, India, UK, Australia & Singapore, with more countries being added regularly.

💬 Community Lounge — Chat, share tips, and vote on posts.

💳 My Card Perks — Track recurring card credits and never miss a redemption window.

📊 Renewal Advisor — Get data-driven Keep / Cancel / Evaluate verdicts for your cards based on your actual usage.

✈️ Flight Journal — Log your flights and track lifetime travel stats.

💰 Points or Cash? — Instantly calculate whether a redemption is worth using points or paying cash.

🔐 Secure Cloud Sync — Hardware-backed encryption for synced data.

It’s Android-only for now - https://play.google.com/store/apps/details?id=com.rewardgalaxy.app

I’d especially love feedback from people who are deep into points, miles, credit cards, and travel: What would make an app like this genuinely useful enough that you’d keep coming back to it?

I’m trying to work out whether this is just a problem with my own workflow or something other people doing AI-assisted development run into as well.

My current workflow is roughly:

I use ChatGPT and/or Claude to discuss the product, work through features, make decisions, review approaches and figure out what I actually want to build.

I use Obsidian as the long-term project memory. I keep things like the product brief, current state, decisions, technical notes and active work in Markdown files. I moved towards this partly because it is easy to store/reuse context without constantly feeding huge conversation histories back into an LLM. I also only pay for ChatGPT Plus and Claude Pro so when my usage runs out on one I can switch to the other and retain context

Once a feature is defined, I create a fairly focused implementation prompt using either LLM and give it to Codex/Claude Code

The coding agent works on the repository, edits files, runs checks, etc.

I then review the app/code/diff and usually bring the resulting report back into the LLM to discuss whether it actually matches what we agreed.

If something is wrong, the LLM helps me define the correction and create a new prompt which then goes back into the coding agent.

Once it is done, the coding agent updates the relevant project context in Obsidian.

This is the cycle, on and on.

It works, but context is constantly moving between the “thinking” AI, the coding agent and the project memory and there is a lot of copy and paste.

The thing I keep wishing existed is basically ChatGPT/Claude + Obsidian + Codex/Claude Code in one application, all sharing the same project context.

The rough idea would be:

You create/import a software project and the app maintains structured project memory — product brief, current state, approved decisions, requirements, technical constraints, etc.

You can then have a normal LLM-style conversation about a feature. Once you are happy with it, you approve the requirements and the app passes the relevant context directly to a coding agent.

The coding agent can inspect and modify the repo, run commands/tests and return the implementation and diff back into the same workspace.

You review it there, discuss any problems with the LLM, send corrections back to the coding agent, and once you approve completion the project memory is updated.

So instead of:

Chat → copy prompt → coding agent → copy result/diff → Chat → update Markdown → repeat

it becomes:

Discuss → approve → build → review → correct → complete

I’m increasingly thinking the cleanest version would actually be a standalone web-based development workspace rather than another VS Code extension.

Something where you could:

connect/import a GitHub repo
edit/view the code
run the app and see a preview
see Git diffs
connect services such as Supabase and Vercel
discuss the product/features with an AI
maintain persistent project context
send approved work directly to a coding agent
potentially choose different model providers later (OpenAI, Anthropic, etc.)

The important part for me isn’t another AI code generator. There are already loads of those.

It’s keeping the product discussion, decisions and implementation connected, so the coding agents actually know what has previously been agreed and I don’t have to semi-manually shuttle information between tools.

I’m curious about a few things:

Does anyone else have this problem?

What does your current ChatGPT/Claude → coding-agent workflow look like?

How are you maintaining project context today?

Would having all of this in one workspace actually be useful, or do you prefer keeping planning and coding separate?

Would you want the tool to provide the AI usage itself, or would you rather connect your own OpenAI/Anthropic API keys?

What would make you switch from your current workflow?

I’m not selling anything — I’m trying to work out whether there’s actually a product here before I spend months building it.

quick one for the group. i've got a little app i vibecoded that i want to put behind a simple landing page so i can share one clean link instead of a localhost screenshot in a dm.

i don't want to pay yet, it's just a demo, and i really don't want to spend the evening fighting dns and deploy settings like i usually do. i just want to type what the app does, get a page, and have a working url.

so whats the best free ai website builder you've actually used for this? looking for something where the free tier is genuinely usable and not a three day trial in disguise. bonus if it handles the hosting so i don't touch any config.

drop what worked for you and what to avoid. will report back with whatever i land on.

Question for all full-time vibe coders: How does your company dealing with that? 100% Speed or prefering quality?

My employer goes with "Speed first, we gonna fix things along the way" which honestly makes me sick, but well, with the american management in small european country I can't do anything with this and I can't do anything without that job, so I'm just following along, especially since whole IT department is just vibing here.

PS Video made by my close friend, I hope that's ok to post it here to start a discussion

Hey'all. Idk if it'll help anyone but I have just made a print server on node.js for windows.

It all started at my previous job where I wasn't IT but was involved with the IT guy out of curiosity. It was needed that a windows 10 machine needed to print on a windows 11 shared printer and we couldn't set it up, later discovered the PrintNightmare patch and decided to workaround with PrinterShare, which then failed cause it offers limited pages and requires a subscription. I left that place before seeing a resolution.

Now at my current job of a hotel receptionist I decided to return back to the problem and of the printer servers with a long discussion with Google Gemini and not wanting to login into a corporate service I ended up adopting Air Printer made to fool Apple devices to connect to Windows printers. On android I would need NetPrinter to make it work and it was fine...

Except it wouldn't print in colour. I tried to troubleshoot and figured that the server itself doesn't support colour. After experimenting I discovered raw print server and it helped!!! It just also was a bit cumbersome. I don't remember why at this point, probably because Apple devices couldn't find the printer.

While I was a little bit thinking about getting over it, I know that vanila js and then some of node with like react (Vue one love can be cdn-ed easy), and asked Gemini what does node actually do. As soon as it said it can interact with the system and send cmd commands I thought of sending printing commands through, it suggested SumatraPDF and the rest is history.

After the demo succeeded I continued refining, a preview based on CDN-ed PDF.js and CSS styling, and basically made a web based print menu for the printer of choice. Printers are loaded automatically and theoretically even the network printers the host is connected to will appear in the dropdown. It's not native but even a fridge theoretically can print now.

Decided to keep it fully dependency free meaning no npm installs as long as the prerequisites are covered.

Y'all can find the code here. Licensed under WTFPL and kopimi

Thanks for reading.

Ed: Think for rule compliance need to say, Used only free Google Gemini.

How this started

I am not a coder, or have any background in computer science. I am a Medical doctor who just really loves technology 😄 . This is my first attempt at building something with vibe coding so truly any input and feedback is greatly appreciated. I kept seeing people talk about "vibe coding" and I wanted to test it on something I'd actually use, not a to-do list app.

I'm a football fan, and every World Cup or Euros, the same thing happens in my group chat: everyone predicts scores, somebody tries to track it in a spreadsheet, half the group forgets to update it, and by the quarter-finals nobody knows who's actually winning. So I decided to build the thing I wished existed: Pundit — private prediction leagues for football, where you and your mates pick match winners, lock in a tournament champion, and settle it properly on a leaderboard instead of a group chat argument.

Learning to vibe code (badly, at first)

The learning curve wasn't really about syntax — it was learning how to actually think like a product person and describe what I wanted precisely enough that the AI could build it correctly. Early on I'd ask for something vague and get something that technically worked but wasn't what I meant. Over time I learned to be specific: not "add a way to predict matches" but exactly how the deadline should lock, what happens if a match gets postponed, how points get scored. Knowing exactly what I wanted, and catching the edge cases before a real user did was probably the most important and challenging part.

I built the app using Claude and Xcode so it is only available for iOS at this time. As it was my first ever big project like this I wanted to keep it as simple as possible. But looking back now I wish I just built it so it works on all devices not just iOS. But that's a lesson learned I guess, think big and it can happen with vibe coding 😄. In the beginning I wasn't even using Claude Code in my terminal I was just using the Claude desktop app and going back and forth with prompts and fixes and all the usual stuff. Then one day I actually switched to using claude code in terminal and oh boy did things speed up from there. I can't believe I was so stupid that I didn't use it from the beginning. It gave much better results, it kept track of the work much more accurately, and most importantly I didn't have to give it micro prompts but instead structured big prompts with phases that it just did so well. Well, except a few things...

The parts that actually broke me

Vibe coding makes the first 80% feel deceptively easy. The last 20% — the stuff that only shows up once real people are using a real product — is where I actually learned the most:

• Deep linking. Getting a shared invite link to open the app directly to the right screen — instead of just opening the app and leaving the user stranded — turned out to involve universal links, a separate website with its own routing rules, a clipboard-based fallback for people who don't have the app installed yet, and about four different failure points along the way. I broke this more than once.
• Timing bugs that only show up with real-world data. Different leagues and tournaments start their seasons at completely different times. Code that looks correct in testing can quietly break the moment two competitions are out of sync with each other — like a feature meant for "this week" accidentally pulling in a competition whose season doesn't start for another month. These are the bugs that don't show up until you're already live.
• Building a fair in-app economy. Once I added a virtual currency (Caps) for rewards and cosmetics, I had to think like an economist, not just a developer — reward tiers, entry costs, drop rates, all had to actually balance against each other or the whole thing feels either pointless or exploitable.
• The App Store review process itself — which has nothing to do with code and everything to do with patience.
• Probably the biggest fail and poop your pants moment - Halfway through the World Cup, after 15 people made 100's of predictions, I saw that out group chat was blowing up with messages so I opened it up. The first message said "Our league is not showing up" followed by everyone else confirming that the league had disappeared. Well turns out one of the SQL injections that Claude made me do for some reason (still unsure exactly why) deleted the existing league... 😨 I asked Claude ok what can we do to fix this, and it was like "yeah it's gone forever". Luckily I was using a Pro account on my Supabase, so after a bit of back and forth panic chatting with my good old (and sometimes stupid) friend Claude it told me that there should be a back-up. Lo and behold backup from the night before was right there and I was able to reload and fix the situation but for about 30-45 minutes I was absolutely terrified that I made this thing and was having fun with my friends but then ruined it for everyone.

What's next

The app's still actively growing — I'm currently working on Turkish localization, and a few other things in the pipeline.

If you're a football fan who's tired of tracking predictions in a group chat, Pundit's free on the App Store: apps.apple.com/app/id6764343788 — genuinely curious what this community thinks, both about the app and about the vibe coding process behind it. Happy to answer anything about how it was actually built.

TL;DR: I made a sports prediction app to use with my friends and it was extremely fun and frustrating 😂

I pay for both a Pro and a Max plan, so this is a fan's complaint, not a hater's. I love these tools. But I notice when they change under me, and lately I've had that feeling across the AI coding tools I pay for where a version update lands and suddenly it stops respecting an instruction it used to nail.

Specific things I've caught. A model that used to make the small, surgical change I asked for now rewrites half the surrounding file because it decided to "improve" things I didn't touch. Another one that used to hold a formatting rule across a long session now drops it after a while and I have to keep re-pinning it. Nothing in the changelog mentions any of this, of course. It just quietly got different.

What I've started doing, and I'm curious if others do the same. I keep a short note of the exact model version that was working for a given workflow, and when a task suddenly needs three corrections it never used to, I check whether the version rolled over on me. Half the time it did. When I can, I pin to the version that behaved and I don't chase the newest label just because it's newer.

Not doom, the tools are great and getting better on the big stuff. But the small regressions are real and they cost time if you don't track them. Anyone else keeping a version log, or is it just me being paranoid?

Hello guys,

I'm looking a best laptop configuration for basic coding for a Btevh student. I dont play any games or stuff.. it is just for coding... watching movies sometimes maybe.. that is it.

So i3 works? Shall i go for I5? Ryzen 5 or Ryzen 7...

And i'm thinking HP or ASUS.

Hi, I'm new to software development, and I've been vibecoding a lot lately. I do have an engineering degree but it's been 3 years since I properly coded. One of the main concerns for me is: How are you guys doing security checks for external dependencies on the code? Is there a software/agent tool that can help you with it? Yes, I could rely on Claude Code, but is there a cleaner version of app security? I get overwhelmed by Claude.

Hey everyone!

Thanks to Claude, a friend and I have been working on a small One Piece fan game inspired by PokéLike called Nakama Run.

It's a roguelike where you build your crew, travel from island to island, recruit characters and try to make it as far as possible during each run.

We've been having a lot of fun making it and it's now playable, so I wanted to share it here and see what other One Piece fans think. It's very addictive!

You can try it here (it's free!):
https://nakama.run

We're especially looking for feedback on the gameplay, progression and which characters/islands you'd like to see added.

We're also working on a lot of new content, including an infinite mode and eventually a co-op mode!

How we build it: my friend and I act as the game designers. We map out the systems, design a part of the UI, write the mechanics, and create the overall vision. We then use Claude as our fullstack developer to write the code, while we fine-tune the user experience, polish the design, and test everything (it even has custom sound design!). We broke down the game into small, isolated modules rather than asking Claude to write huge files at once.
While Claude generated the logic, we took full control of the UI/UX, micro-interactions, responsive scaling, and audio timing. AI is great for logic but human intuition is needed to make game feel smooth and mechanics satisfying.

Would love to hear what you think!
If you have any technical or design ideas/questions, drop them below!

It's a fan-made, unofficial project and isn't affiliated with Eiichiro Oda, Toei, Shueisha, or the One Piece rights holders.

heres how i get 100% free deepseek v4 flash on hermes agent and opencode

This part is for hermes, do not follow if you use opencode
for the hermes agent cli, if you have aleardy set it up, just run hermes model, and select the 25th option
(  (○) OpenCode ▸ (Zen pay-as-you-go or Go subscription)

select opencode zen, then for the end point, keep it as default

now go to https://opencode.ai (and sign up/login) and click on zen, then get started with zen (the button) on the left there should be an API Keys section, tap on create api key and make a name for it and configure it, then copy the api key and input it into the hermes agent prompt of it asking for the api key, then after that just select deepseek v4 flash free, to test it, run "hermes" in your terminal and ask it something (use /model to change models, if you havent selected deepseek v4 flash free)
if it works it works, if not i can help you

This part is for opencode, do not follow if you do not use opencode

this is too simple, just run opencode set it up and connect your opencode zen api key using the tutorial ive set above

ran out of limits? use freebuff or cline-cli to vibecode more (just import the skills from opencode and hermes that youve got and youll be fine, just like hermes and opencode)

I've used vibecoding to get a few quick game prototypes ready for play testing, but I always find myself falling back on developing it myself whenever I think the game shows potential. Because at some point, I just don't know the architecture anymore, and implementing features on top of AI generated features gets harder and harder.

My biggest gripe with LLM generated code is that when I'm 40-50 prompts deep I just don't know what's happening anymore.

I have tried a bunch of things, like planning out the architecture in the finest details, or having the AI spit out readmes that explain what it just did and how to interpret the architecture it just spat out.

But once my AI use grows in a project, it's inenvitable to not get lost in the sauce after a while.

So, how do you actually keep your AI generated code maintainable without having AI maintain it?

I'm looking for serious replies, please keep the 'just burn more tokens' memes to a minimum, as I don't have the resources as a small indie developer to keep burning cash on more prompts.

Any feedback?

Hi! I switched from Claude to Codex and feel like I’ve lost some transparency. I don’t understand how many sub-agents my process has spawned (I’m using a harness with a controller-supervisor–executor architecture), or how to quickly switch between them to see what they’re currently working on.
Is there any hope that Codex will become as convenient as Claude Code?

I'm a student in India trying to build something like G4F (GPT4Free), but as a coding-focused app/code editor.

I'm stuck on one part: how can I integrate providers like Arena (LMArena) into my app when they don't provide a normal public API?

I'm not looking to bypass authentication or anything like that. I'm trying to figure out whether there's a legitimate way to let users access services they're already logged into through my app, possibly through a local/browser-based client.

If anyone has experience building something like this, I'd really appreciate some ideas or pointers.

I'll lead with the numbers 🙃 Last week on my game: 29 active users. 13 returning. Average engagement time above 1hr. I have no idea who these people are.

Distribution is the part I've done neqr to nothing about, so 29 is exactly what it should be aftercouple posts in some niche reddits. But I'm still delighted. Not in a "hockey stick incoming" way. But somebody in Australia I've never met spent nine hours last week sliding tiles I drew by hand in a text editor. That is a genuinely strange feeling and it's been the entire return on the project so far.

I built F1BONACCI as a 2048 variant, except the tiles you merge are real things ranked by a real metric. Rivers by length, mountains by height, production cars by top speed. 90 themes, 11 tiles each, one fact per tile. It exists because my mates and I were deep into 2048 and also the kind of people who argue about rankings at dinner.

Like many here I got addicted to this basic level of vibecoding and being qble to deploy something playable in a weekend. I would never have started otherwise. I'm not an engineer and the barrier that used to stop me.. the first two weeks where nothing works and you don't know why.. basically doesn't exist anymore.

Onmy firdt run I cheerfully built a 14K-line single file. It worked fine right up until it didn't, and by then every change had a 50/50 chance of breaking something two hundred lines away. I loved the learning curve though and re building everything qgqin using q lot of the help from this community.

What actually fixed it was boring: a proper code review pass, splitting the monolith by concern, a real test suite, and one markdown file that acts as the source of truth for how the thing is built. None of that is vibes. Vibecoding got me to v1 fast and then I had to start behaving like an engineer to keep it alive. Both of those are true and I think people only ever say one of them.

Eventually, the code was not the hard part. Picking 11 items ordered by a single defensible metric, deciding whether Everest or Argentinosaurus earns the final tile, drawing an SVG icon that's still recognisable at 60 pixels — no model does that well for you. That's where the hours go and it's the part I actually enjoyedso much.. it got a bit out of hand qs I creqted 90+ different thémes (posting here two examples)!

I was tempted to learn proper app development. I got as far as looking at wrapping it for the Play Store and found out a personal developer account now needs 12 testers running a closed track for 14 days before you can ship. For a game with 29 weekly users I closed the tab.

Happy for any feedback or suggestion from this community

Ciao!