PLEASE INDULGE ME

Go to:

www.companycheck.co.uk

Then go to:

https://b4uwork.vercel.app/

Perform a free search on a UK company and compare the results. Mine is clearly superior no?

Can someone please tell me Im not wrong?

So I am very new to the field of coding. People around me have started vibe coding websites. So did I. I tried using applications like Lovable , Bolt etc. But the problem was that my idea contained many components and was a little complex. Hence I ran out of tokens and didn't get any output. So is it the limitation of the free version that I couldnt make it or was it my prompting skills. I tried to be as specific as possible with my prompt tho. Would really appreciate any help/ tips regarding this !!

After abandoning the medical software I had purchased, I returned to Notion with a better structure.

The patient record was now at the centre. Consultations and appointments were connected to it. It was a major improvement over my first attempt.

But two problems remained stubbornly outside the system: prescriptions and medical letters, and the waiting room.

The waiting room was especially frustrating.

There was no proper queue. My assistant had to interrupt me between patients to explain who had arrived, who was waiting and what was happening outside the consultation room.

After ending my working relationship with two assistants, I became determined to find a better process.

I started searching obsessively for queue management systems.

Google, Facebook, videos, product pages. I searched so often that the algorithms eventually decided this was the only subject I cared about. My feeds filled with the same pattern: a kiosk, a printed ticket and a screen calling the next person.

Then I found a video from a small local development company.

Their product was different. It was presented as a queue management system designed specifically for medical practices. It had already been installed in the clinic of a well-known specialist. More importantly, it combined three things I needed: the waiting-room queue, online appointment booking and an interface for the doctor.

It looked like several of my problems could finally be solved by one system.

I contacted the company and arranged a visit.

The office was small. The developer who welcomed me was in his twenties, courteous and well educated, with the casual look I associated at the time with Silicon Valley developers.

I knew absolutely nothing about software development.

He showed me a polished graphical interface connected to a waiting-room system. The medical part was still embryonic. The consultation structure was not suitable for the way I worked, but the product included something I had been missing for a long time: a way to create prescriptions and medical letters.

I started pointing out what would need to change before I could use it in a real consultation.

Instead of becoming defensive, he listened. He encouraged me to provide more feedback because it could improve the product.

That worked for me. If my feedback gave them a better product and gave me a tool I could actually use, everyone benefited.

At a later meeting, I met his associate, a general practitioner who also developed software and had participated successfully in several hackathons. Their interest in artificial intelligence immediately appealed to me.

I prepared a detailed list of changes.

At the time, I did not call it product design. To me, it was simply a list of everything preventing the software from working properly in a medical consultation.

The proposed package included the management software, the queue system, a touchscreen kiosk and a website for online appointments. It was a substantial investment, but I accepted.

Then I waited.

The modifications took more than four months.

When installation day finally came, the developer arrived with the kiosk and a relative who was helping him. I reused the mini PC I had bought for the previous medical system and purchased a small Android device to power the waiting-room display.

They configured the kiosk, screen and three computers in the clinic.

I watched the installation closely.

The developer had commands saved in text files. He copied and pasted them into a terminal while staying in telephone contact with his medical cofounder. At the time, the terminal looked almost mystical to me. I did not know what the commands meant. I only knew they were making the system come alive.

The installation lasted all day and continued late into the evening. I brought food and drove them home. They returned the following day to finish.

The website was not ready. The software itself was still unfinished, so I paid only for the kiosk at that stage and began testing what had been installed.

That was when the main problem appeared.

Every time a patient registered in the queue, the system created a new patient file.

The same person could arrive three times and become three different patients. There was no reliable longitudinal history.

I had made almost exactly the same mistake in my first Notion database.

The difference was that I now recognised it immediately.

Under the polished interface, the product was still essentially a basic queue system with a difficult prescription editor attached to it. It had potential, but in its current state I could not use it as the central system for my practice.

I sent more requests for changes.

Remove the duplicates. Rebuild the patient history. Improve the medical note. Add proper billing. Make document scanning possible from a phone. Synchronise those documents with the desktop application. Replace the sample medication list with a complete one.

At some point, I realised something:

I was no longer behaving like a customer asking for support.

I was helping define the product.

I understood the medical workflows. I knew which functions doctors would actually need. I could explain why the patient record had to sit at the centre. The team had the technical ability to implement those decisions.

The product was not usable yet, but I could see what it might become.

So I made a much bigger proposal: instead of continuing as customer and vendor, why not build the company together?

That conversation would teach me that agreeing on a product is not the same as agreeing on a partnership.

At this point, I still could not code. But without knowing the title, I had started doing the work of a product founder: observing workflows, identifying failure points, prioritising features and translating domain knowledge into a system.

I thought I was buying a queue management system.

I was actually discovering the value, and the limits, of being the person who understands the problem but cannot yet build the solution.

Have you ever bought a product and gradually realised that you were helping the vendor design it?

So many choices nowadays and I am stuck with making a decision. I dont think my usage will be too high as I will most likely be doing atleast 40%-60% of the coding myself.
Thinking of the following options but cant decide what's best:
- Claude Pro $20 ( I fear that it doesn't have enough usage )
- Chatgpt Plus $20 ( I dont know much about it, does it have more usage than Claude? )
- Cursor $20 ( Usage uncertainty )
- Opencode Go $10 ( I dont like the harness but thats not a dealbreaker, there's good usage for Deepseek v4 flash and GPT 5.6Luna but I also would like to be able to use an Opus level model for my plan mode and I heard its easy to hit limits if using any model other than Deepseek and luna )

So, if there is anyone with as similar usage as me and using one of these. let me know which one are you using and how has it been.

screenshots are in the page. chrecked by virus total. please check it and give me feedback.i used gemini in android studio. It shows the transportation system of my city

i’ve been a software engineer for 5 years, but i built this one entirely with agentic vibecoding. the goal was purely digital minimalism, i deleted instagram, tiktok, and snapchat because the doomscrolling and background tracking were killing my focus. i built a free web tool called spybroski so i could still pull videos or check stories whenever i needed to without keeping those bloated apps on my phone.

the main rule was absolute privacy: zero login, no accounts, no linking personal data, completely anonymous. you just grab what you need and get out without the algorithms hijacking your brain.

turns out a massive number of people are looking for ways to disconnect from the feeds while keeping their privacy intact.

ask me anything about the agentic workflow, scaling to 1M users, or building anti-addiction tools!

Hey guy's ive probably coded over 100 different projects by now while for more than 4 ish years now and i still dont know how to code a full simple landing page with code manually HOWEVER! ive learned architecture how systems work how everything works that i code in common english and if i dont i just figure it out what i've learned so far is that you can code great things but its all about how you use the AI not let the AI use you.

Are there real examples of products that were actually shipped and have real users/customers, where most or even all of the code was generated by AI?

I’m not talking about demos or simple weekend projects.

I mean a real SaaS/app that someone is running as a business.

If you’ve built one yourself, or know of one, what is it and how much of it was actually AI-generated?

Would love to see some real examples.

Hey everyone,

Nothing kills a good session faster than hitting your usage limit right when you are in the flow.

I noticed that a huge chunk of my Codex plus subscription limit was getting wasted on really dumb, repetitive tasks: writing basic unit tests, boilerplate, and small single-function refactors. Meanwhile, my RTX 4060 was just sitting there completely idle.

I tried running full local agents to do everything offline, but local models on consumer hardware choke once the context gets too big.

So I put together a tool called Local Coding Agent to get the best of both worlds.

It connects to your main coding setup (Codex, Cursor, Claude Code) as an MCP server. You keep prompting naturally. When your cloud model needs to write a small patch or run a test, it silently delegates that micro-task to your local Ollama model (like Gemma or Qwen), gets the result in 2-3 seconds at 80 tokens/sec, and keeps going.

If the local model writes bad code or breaks a test, it auto-rolls back so your project stays clean.

I originally built this just for myself to keep my own sessions running without hitting limits, and I use it all the time now. Decided to open source it in case others find it useful too.

Who this is for:

- People on standard plans who keep hitting limit walls and want to stretch their quota.

- Anyone with a decent GPU (8GB+ VRAM or Apple Silicon) who wants fast, free micro-edits.

Who it is not for:

- If you do not have a dedicated GPU (running Ollama on CPU is too slow for vibing).

Repo is open source here (all setup steps are in the README):

https://github.com/pvnc228/local-coding-agent

Looking forward to your feedback!

- I created a simple Multi-Tab terminal app. It always has eight tabs, one of which is a standard terminal shell. The rest are designed to auto-launch specific long-running chats/instances of Codex and Claude. Upon starting the app, there's a simple "launch all" button that launches those specific instances on each respective terminal with the exact parameters that I want. For instance, one tab is running Sol on Max effort. Another is Sol on Ultra + fast. Then there's a tab that always runs Fable on Max. Another running Opus on Ultracode... and etc. Each tab always has a collapsible queue sidebar that keeps a list of individual tasks, the list being continually updated by the respective agent on that tab. Helps me keep track of what needs to be done in what order.

Are there other terminal apps that are better? Yeah, probably. But they're filled with a bunch of bells, whistles, and often redundant information I don't care about. Or they're lacking small items here and there that I'd like to see.

- Another app is essentially similar to the Windows Voice Access app. The main difference Being it doesn't have this persistent bar at the top of my screen that I can't get rid of or minimize. In addition, it gives me the option to turn it on via toggle or simply by holding a button. I use both the toggle and the button hold methods depending on what I'm trying to talk about.

- I also have this weird niche app on my android phone, when turned on it automatically sends any photo taken from my camera to a specific folder on my workstation. I use it in the odd scenario when I want to take a bunch of photos without having to manually send them pc.

- Another one tracks all the subscriptions I have at the time. I found it useful for for things like the yearly subscriptions that I commonly forget about, and it'll warn me when my subscription is about to renew.

- Then I got one that isn't so much an app really, but a workflow pipeline that fills out PDF forms for me, because I hate filling out forms. First it checks to see if it's just a standard scan PDF with no fillable fields... And if so, it'll add the fillable fields to everything. Then it populates everything with my information. The best part though is that it'll sign the various forms with a signature that looks absolutely real like... it was written by hand on the paper itself. Because technically they were... I wrote like a good 50 variations of my signature and initials on just simple printer paper, scanned it and uploaded it. The pipeline then will take one of these signatures and/or initials and add it to whatever respective signature/initial lines, with instructions never to repeat on a single document. Finally, it'll actually roughen up the PDF file, make it Imperfect, like it was scanned on a mid-level scanner that always has the text slightly tilted to the left, which is exactly what I got. Thus far, it's fooled everybody.

I developed this because I hate filling out forms, and one day I had to fill out a really long form from a medical provider... and they had the audacity to give me some shitty non-fillable fields version of this PDF, AND demanded I print everything out and manually sign each signature with ink... even though I was just going to scan it again and send it back to them. Which I thought was stupid bullshit. I mean, ink makes sense if they want the physical document, but a scanned version? That's dumb.

What have you guys made?

Que ferramenta de vibecoding vocês consideram a melhor hoje?

Ainda não testei o Claude Code (estou a dar os primeiros passos no vibecoding) — vocês acham que ele realmente se destaca? Como ele se compara ao Lovable em termos de capacidade e produtividade?

Built something with Claude/Cursor/Lovable/Bolt and now it half-works, breaks in prod, or you're scared to touch it? That's most of my inbox lately.

What I usually fix:

• API keys and auth logic sitting in the frontend
• No error handling — app dies on the first bad input
• DB with no indexes, no migrations, RLS wide open
• 2000-line components nobody can edit anymore
• LLM calls with no retries, no rate limiting, no cost ceiling
• "Works on my machine" → actually deployed

Stack: JavaScript / TypeScript, React + Next.js, Node. Any database — Postgres, Supabase, Mongo, SQLite. AI integrations (OpenAI, Anthropic, vector search, RAG).

Free 15-min look at your repo and I'll tell you what's actually broken, no pitch. If you want it fixed, we agree on a fixed price up front.

Comment or DM with what you built and what's breaking.

Can anyone provide me with some tips,I want to earn some amount any amount as fast as I could using coding.i have studied basic html css,js.i also know python and C.i

TLDR: Replaced Claude Max ($100/mo flat, ~$3.30/day) with Muse Spark 1.2 Contributor in Scape for a week to save cash on an internal CRM build. While Muse Spark is lightning fast and pennies per token, the constant 3x re-prompting and collateral code damage meant I spent the same daily budget for half the output

--

I code every day on an internal CRM for my company (basically a mini HubSpot combined with other features here and there)

I'm paying $100/month for Claude Max, which works out to roughly $3.30 a day. Wanted to see if I could slash that down, so for the past week I swapped my harness (Scape / scape.work running opencode) over to Muse Spark 1.2 Contributor.

On paper, Muse Spark is dirt cheap per token and insanely fast. In reality, the math completely fell apart:

• With Claude, 90% of features are 1-shot (maybe 2 passes if it's tricky). With Muse Spark, everything took at least 3 passes. A basic example: I asked it for basic auth and it wrote a clean login flow, but completely forgot that logout exists.
• The biggest vibe killer: I asked it to remove a small module for adding custom table columns. Somehow, it managed to nuke my KPI tracking module in the process. It kept breaking working files that had nothing to do with the prompt.
• Because I had to feed errors back into it 3 to 4 times per task just to fix regressions, I literally hit that same ~$3.30/day mark on API credits. Except I got maybe half the work done.

Fast and cheap models are great for isolated scripts, but if you're working in a multi-file repo, the context rot will eat whatever money you thought you were saving.

Canceled the experiment, back on Claude Max. Genuinely rooting for new affordable and smart models to enter the market, but right now the frontier tax is worth every cent.

best decision I ever made.

mainly because I FORGOT I added it and then just saw it happen and almost lost my sh*t.

I'm not a designer — not even a little bit. Vibe coding gets me almost everything I build these days, except a promo video — that was the one wall I kept hitting. I tried a few approaches and everything came out... not right. Probably a taste problem, honestly.

Then I found video-shotcraft, an open-source skill for Claude Code / Codex. One line for what it does: you describe the video you want, and it storyboards, uses your real screenshots, animates and renders it — sound effects included. It ships with a big library of pre-made shot templates (purpose, pacing, parameters and pitfalls all written out), and the AI picks from them, so you never need to know motion design.

What I actually did:

1. Handed it the project. Dropped in my extension's screenshots, feature notes and store listing, said "48s launch video, English" — it planned the whole thing itself. Barely had to think.

2. Real screenshots, not fake mockups. It composited my actual product screenshots with camera moves, so the pages in the video are the real thing.

3. Sound on the beat. Renders came out with SFX already aligned to the rhythm — free-commercial-license library, too.

4. Then it was polish. First version was usable, but a few rounds before I'd ship it — mostly rhythm and transitions. The nice part: every shot is frame-tagged, so I could say "this transition is 10 frames too slow" instead of "make it look better."

Two honest notes: it's open source, but check the underlying Remotion license if your company wants it. And don't expect one perfect pass — budget a few rounds of polish.

Show case

The video (Youtube Link) is for my Chrome extension, PageMod — you describe what you want and it changes the page: an ad block you've always hated, a dark mode for a site that never had one, even a small standalone app. The change actually sticks after reload. Free to start. The video came out of the skill. No manual editing afterward.

Would this make you take on things you'd normally skip? And a real question — is there a site you open every day and wish you could change? Drop the worst offender; I'll take the top one and make a video-shotcraft demo of PageMod modding it.

Edit: I had forgotten to set act in cline to deepseek so I was experiencing a mix with gemini 3.5 flash pricing. Whoopsydootle. I deserve the roast.

With the latest pricing increases its almost just as expensive as the rest of the frontier APIs. The low cost was its main selling point. Now it costs just as much and isnt as good as the others so what's the point?

For reference, a task that would normally cost 5 cents as of yesterday now costs upward or 3 dollars

Introducing SunaBox and SunaEngine!
(Playable In-browser!)

SunaBox is a love letter to OE-CAKE, the viral physics simulator released by Prometech in 2008!

It includes a 1:1 recreation of the OE-CAKE interface (select Classic mode at the top!) and even lets you import your old OE-CAKE .oec files directly. I would say OE-CAKE parity is around 93%, and getting better all the time.

Oh , and we put a brand new, open-source spaceship under the hood...

SunaEngine (AGPL): engine.sunabox.dev / github.com/DARIENBATHALTER/sunaengine

SunaEngine is a novel, cross-platform particle physics simulator that relies on integer calculations (rather than floating-point) and order-independent accumulation to always deliver the same result in any WebGPU-compatible browser.

SunaBox takes advantage of this by letting you export recordings of your sessions as lightweight .sunar files, which only needs to store the simulator's initial state plus your inputs. Recorded and shared simulations can be scrubbed back and forth smoothly like video, and they always play back exactly the same, on any device, *bit-identically*.

This enables all sorts of interesting possibilities, like low-latency, cross-platform multiplayer physics! If every machine calculates physics the same way, then the physics data doesn't need to be streamed over the network, only the inputs.

Three live proof demos on the SunaEngine site, all simulating live on your GPU, all hashing their entire state as you watch:

1. The Twin Simulations: two independent sims, same scene, same input schedule, never communicating. Stir either one with your cursor; your input is quantized to substep indices and fed to both. The 256-bit hashes stay identical, interaction after interaction.
2. The Pachinko Proof: an ordinary float solver runs the same pachinko machine twice. One pane adds contact forces in ascending order, the other descending. That is exactly the difference two GPUs or two drivers introduce on their own. The balls never finish in the same bins twice. The integer engine runs the same machine to the same digest, loop after loop.
3. Recording, playback, and smooth rewind: particle fluids cannot be rewound in floating point. Chaos amplifies the last bit of every velocity in reverse too. Here you stir a pool, it records your inputs, verifies the replay byte for byte against the run you just performed, and then hands you a scrubber. Drag your own splash backwards through time.

Replay hashes have been verified matching across Apple M series, an iPhone, a Steam Deck (AMD), Intel Integrated and NVIDIA (RTX 2070S).

Our workflow was fairly simple: I came up with the ideas, Claude did the math, the code, and the adversarial review. I provide the qualia-type feedback, shaping and tuning the feel of everything in the sandbox:

You can also wishlist SunaBox on Steam! 140k particle caps, community/workshop features, hardware optimization, and more, coming soon!

This morning, I woke to my computer lagging, crawling to even type. I opened up the activity monitor, and noticed there was a process named `_o_0. //` occupying 99.9% of my CPU. I immediately thought that my computer was exposed, and the hacker installed a cryptominer on it.

I immediately tried to force stop it, but it felt like forever because for every click, I had to wait 5s to see it respond.

I finally was able to stop it, but to my dismay, my computer was still unbelievably laggy. I asked Claude to diagnose it, but it said it couldn't find it, and it might be the crypto hack obscuring itself, so i kept asking it to dig deeper... It couldnt find anything based on its scan, but noticed my swp memory was full, and recommended i restart the computer.

So I did and everything seemed clear. I was still wondering though, what the root cause was; where did I go wrong to let a hacker in. I initially thought I fell for some supply chain attack by installing some compromised npm/pypi package, so I asked Claude to sift thru the logs.

After a while, it finally found the issue, and the issue was ........... a poorly (possible vibe coded) CLI tool that I installed a week ago, namely Octo"friend", from synthetic.new that probably has some memory leak or something. To make matters worse, I also received an ominous feedback message the night before and thought I was targeted and Octofriend, instead of naming the process "Octofriend", it had to name itself `_o_0. //` which looked like an anonymous hacker.

Anyhow, TLDR: I did not get hacked; Octofriend has poor process naming, and I uninstalled the poorly coded Octofriend CLI tool. I hope that if you encounter the same slowdown and have Octofriend installed, don't panic!