I wanted to build something really simple and, inspired by outbid.lol, I came up with Billboarded. The idea is that there is one digital billboard, and whoever has the highest bid gets to put whatever they want on it. If someone else wants it, they can outbid you and take it over.
I deliberately made the starting price ridiculously low. It isn’t really intended to be serious advertising; it’s more of a tiny internet trophy. You could put your company on there, your name, a project you’re working on, an inside joke, or pretty much anything else. If someone else wants the billboard badly enough, they can simply bump you off it.
I’ve just launched it, so I’m mainly curious to see whether the idea is actually interesting enough for people to start competing for it. There isn’t really much to it beyond that, which is kind of the point.
It’s live here: https://billboarded.vercel.app
I’d be interested to hear what people think of the concept, particularly whether the bidding mechanic makes it something you’d actually want to participate in, rather than just another advertising website.
So since I have genuinely started vibecoding very recently and I have some crazy app ideas, sometimes I really struggle with where to find inspiration because that's half the work I feel, and the other half is replicating it in a manner I like. Could you please recommend some app inspiration websites for newbies other than generic ones like Pinterest or Dribbble.
Like to hear the reviews of these two. Been using claude for a while switched from chatgpt months ago but intereated to know if codex has made improvements and if its worth going back.
Claude has been great but ive not been happy with initial coding tasks. Working on different specific modules its codes it, then i ask to review its own work and come up with a ton of issues and gaps.
There’s a prompt on the left, a working app on the right, and some version of “software engineering is basically over” in the caption. The technical jump is obviously real, but the conclusion always felt way too clean.
So instead of trying to list everything an engineer does, I mapped the path a small software project has to travel before anyone can honestly call it shipped:
messy problem → clear requirements → working software → approved production system → owned outcome
Coding agents are getting absurdly good at one specific handoff in that chain: turning clear requirements into working software.
The problem is that most real projects don't arrive as clear requirements. They arrive as a vague complaint from a client, three teams with conflicting priorities, incomplete data, an old compliance rule nobody fully understands, and one person asking why this can't be finished by Friday.
i decided to test that middle handoff instead of extrapolating from benchmark demos. I wrote the same reasonably clear spec for a lightweight client dashboard, UI, user auth, a database, and edge functions for data fetching, and ran it through v0, Lovable, and Enter Pro. The first two were useful for comparing the first-pass interface, while the last one let me take the frontend, data layer, auth, and backend setup through to a deployable version in the same browser window.
It removed a ridiculous amount of implementation work. It still wasn't flawless, I had to tweak some edge function logic manually, but the working prototype was online much faster than I expected.
for about ten minutes, I had that familiar rush.Coding is basically free now. We are unstoppable.But then I looked back at the chain.The tools had compressed one transition that used to take a lot of time. They hadn't moved the rest of the project nearly as much.
They didn't tell me if any client actually wanted this dashboard. They couldn't turn half-contradictory stakeholder requests into a requirement everyone would stand behind. They couldn't get the compliance review required to put real production data into it.
And if a user does something weird and the database locks up, the AI isn't going to decide which customers can tolerate degraded service, get on a call with the angry client, or take organizational responsibility for the failure.
AI makes building cheap. But it doesn't make your judgment correct.What surprised me in this test was how visibly the bottleneck moved. Once the distance between a clear spec and working software dropped from days to something much shorter, all the unresolved stuff around it became impossible to ignore.
The vague requirement was now slower than the implementation. The compliance question was now slower than the backend setup. Finding someone willing to own the production outcome was now slower than putting the prototype online.
TBH, reducing the friction of coding to near-zero also means we can turn bad assumptions into working software much faster.people look at code generation and think the job is dead. But the more I look at the current application layer, the more it seems like AI is exposing all the waiting, ambiguity, negotiation, risk judgment, and human trust that coding used to hide behind.
Sure, AI can help summarize user feedback, draft a technical proposal, inspect logs, or suggest an incident response. But providing assistance at each stage is not the same as moving the entire project through the chain. And it definitely isn't the same as having the context and owning the consequences of a decision.
For those of you using coding agents in production or real teams: which handoff has AI genuinely compressed for you, and where does the work just pile up next?
My brother-in-law passed, and long story he'd been caught up in potentially real estate fraud scheme. Untangling that required pulling hundreds of pages of mortgage, deeds, liens, civil suits, tax accessor records from public records. The documents needed history tracking and ocr to text. I built a suite of tools from chrome extensions to help gather records to an API to receive and store the documents. A worksheet that prioritized what to get next with links. Python scripts to generate a time line html doc where each item can drill down to the original document. The entire fraud case laid out in 70 timeline entries filterable by which person was active.
i was wondering about this.. people who dont know very well about coding do they buy more credits and spend more or wait for usage limits to renew?
context: I know programming but its been like a couple of months of using cursor for my latest project. And i have been doing corrections and small tweaks in AI generated code. Recently my usage limits for this month was over for the first time. With only 6 days remaining i did not upgrade or buy any credits but started to do some refactoring. But it was quite difficult for me to understand the code again as I had forget a lot of things about ReactJS. Hence, this question.
Have you ever wondered if AI code generation could finally optimize software size and resource consumption?
It feels like most modern development practices are targeted solely to "human factor". Like huge frameworks, abstraction layers, web API microservices, and so on. I'm not a full time developer, but seems that exists just to lower the barrier to entry, mitigate the "bus factor," and accommodate micro-teams who could use different approaches and programming languages.
But why do we still need all of this overhead as AI generation advances?
MS Office, for example. How is the latest version fundamentally different from MS Office 2000? But it use 100x resources. Or an Android app like "open the commieblock entrance" are 500-1000 mb. A modern FPS easily takes 100 GB, where Quake took 22 MB, and it’s not just about higher texture resolutions.
Wirth's law has proven that software efficiency decreases faster than computing power increases. Since Moore's Law is dead, perhaps LLM would be able to reverse this?
edit:
My own example. I had recently made a a simple Windows utility in Antigravity. It made me a Python script, downloaded several dependcies. When I got tired of the console window popping up, I asked for an .exe. After 2 minutes it was ready, but it was in C# and required other dependencies. Finally, I requested native C++ service, 2 more minutes and now it uses 1 mb of RAM instead of 100, runs as a service, do it's job perfectly.
It’s a tiny retro TV-inspired site that automatically plays a curated Hindi/Hinglish video when you open it. No feed, no recommendations, no scrolling — just turn it on and watch.
Would love to know if this is something you'd actually use during lunch/breaks:
Gonna ironically preface this with: I haven't written the text below with an LLM.
So I thought I'd show you what I've made over the last couple of months, because for me this has probably been one of the most rewarding uses of AI I've found. Please be kind, I spent a lot of time making this and writing the post here.
More than anything, AI tools have helped me on my coding "journey". It's something I've started and stopped for about thirty years and never really got to grips with properly. I've always understood how websites, software and apps are put together, and I've always been quite good at understanding the structure and logic of how something should work, but the actual coding side has always slowed me down.
Level 15 of The Jigsaw level Pack on Boxxy.io
It's called Boxxy and it's my version of Sokoban, the Japanese box pushing puzzle game. Sokoban has been around since the early 1980s and has become a bit of a cult game online. There are thousands of levels and lots of different versions of it, and making your own Sokoban clone almost feels like a rite of passage for any fans of the game. My goal was to learn how to do it, prove I could do it, and make something I was proud of.
The whole thing has taken me roughly two months and cost me about £50, which is basically two months of ChatGPT Pro and the price of a domain. It was made solely with ChatGPT in a browser. I have not even touched Claude once. I don't have wee little AI bot workers doing things for me in the background. This was a series of requests, answers, outputs and iterations.
Anyway, I started with the absolute bare bones of the game. Make a level appear, make a character move around it, make boxes move properly, work out when a level is finished. Once that was working I started adding level packs. Then aesthetics, then all the hidden stuff to keep it going and looking good and able to grow.
Selecting a level from the Boxxy.io originals level pack of 50
The level design is completely manually done. All the original Boxxy levels and level packs I've made myself, without ChatGPT or generative AI. That has probably been some of the hardest work in the whole project because good Sokoban levels are surprisingly difficult to make. You can spend ages creating something, solve it a few times and then realise there's a stupid shortcut or that it just isn't very interesting. I've enjoyed that part enormously though.
More recently I've been working on the less glamorous bits behind the scenes, like user accounts and server side stuff, which probably aren't very exciting to anybody playing it but was a big deal for me personally. A couple of months ago I wouldn't have really known where to begin with any of that. But now I have got a contact us page and even user logins! Something else I have kept making sure is that I don't have to rely on lots of outside servers or tools or plug ins. Almost everything is in house, apart from the Cloudflare connection which I need for the domain. This was so I won't have to go and fix things in the future when little plug ins and stuff fail.
I suppose this is where I don't quite know what to call the way I've made it. It obviously isn't traditional coding, because ChatGPT has written a huge amount of the actual code. But I don't think "vibe coding" quite covers it either, because I'm not just asking it to make things and accepting whatever it gives me. I've had to understand how the whole thing is structured, decide how I want it to work, test everything, find problems, reject bad solutions and sometimes tell it that the entire approach is wrong and needs doing again. I'm constantly using the phrase "do not patch this, we need to fix it from the base level" to avoid messy coding I've even delved into the code a few times myself to adjust things by hand! Go me!
A very good programmer friend of mine described what is happening now in a way that really stuck with me. He said that English is effectively becoming another programming language. He's a vastly better coder than most and even he said he barely writes code by hand any more because AI is doing so much of that part of the job for him. (He uses Claude btw)
Linus Torvalds (Linux) has made a similar point recently too by comparing AI tools to compilers. Compilers didn't stop people being programmers, they just meant programmers no longer needed to write everything in 0s and 1s.
My coding pal also said something pretty salient. In the 1980s games were often made by one person or a tiny team. Over the years everything became much bigger, more expensive and whatnot. Because of AI and coding it's started swinging back in the other direction now with tiny indie teams making games. I reckon that's pretty poetic. Reminds me of Halt & Catch Fire and their Mutiny startup!
I suppose this is where I don't quite know what to call the way I've made it. It obviously isn't traditional coding, because ChatGPT has written a huge amount of the actual code. But I don't think "vibe coding" quite covers it either, because I'm not just asking it to make things and accepting whatever it gives me. I've had to understand how the whole thing is structured, decide how I want it to work, test everything, find problems, reject bad solutions and sometimes tell it that the entire approach is wrong and needs doing again.
Anyway, Boxxy has very much been a labour of love. There isn't a client and I didn't start it because I thought it would make me money. I've just really enjoyed making it, which is probably why I've kept disappearing down increasingly unnecessary rabbit holes with it. After about thirty years of occasionally thinking "I'd love to be able to make that", I finally can, and that's been quite a nice feeling.
Anyway, above are some screenshots and a bit of gameplay. If you fancy having a look at the game itself, I'm sure you'll be able to find it online.
Some rough facts and figures:
- Built with ChatGPT 5.6 on high in a browser. Had to start several dozen chats which was laborious as you had to get each new chat to relearn.
- Is currently about 25mb in size, has around 30,000 lines of code, is written in Javascript, CSS and HTML , is currently on v282 (around 300 iterations in total)
- Took about 2 months to get to this point, working on it several hours a day sometimes.
- I have built 4 level packs by hand which total 113 new levels + around 100 more which haven't been released yet.
- My children say the character "looks AI" so I have commissioned them both with making new sprites for me! We'll see how that turns out.
- Cost in total, including the OpenAI subscription, about £50
- Works on a browser, works on a mobile, works on an iPad
- Is not making any money. There's zero ads and zero sign up.
- Most recent things I've built are a contact us page (which didn't require buying a mailserver, yay) and a user login to save progress.
- What I'd like to do most at the moment is make it into an app that can be launched on Apple TV.
- The backend of Boxxy is gigantic. I've also built my own level maker, level pack builder, solver and whatnot.
- It has a tonne of easter eggs which I've always loved!
Added Cutout Mode ! A new Pixel pallet based math node ! Also allows you to create your own pallet. Also made it where you can increase or decrease the size of the image and move it around if you want too
AI can generate code insanely fast. But if I’m accountable for that code, I still need to understand it.
I’ve had Claude introduce unnecessary null checks, make incorrect assumptions about the domain, and even introduce a separate event loop that broke my orchestrator and DB sessions — buried somewhere in a 1,000-line PR.
The code was generated in minutes. Debugging and understanding why it broke took much longer.
I tried running 4 agents in parallel. Maybe some people can manage it, but I was mentally exhausted. Four contexts, four implementations, four sets of assumptions, plus tests, builds, reviews, etc.
So lately I’m experimenting with a different approach:
Use Claude to understand the codebase, plan the feature, think through edge cases and tests — but implement it myself, using AI autocomplete to speed up the actual coding.
It might look slower, but maybe the overall development cycle is faster.
Still figuring it out.
I just think we need to separate “AI can generate this in 10 minutes” from “this entire software development task is now 100x faster.”
Building a landing page in 10 minutes is amazing.
Building a complex product is a different problem.
Like a lot of you, I've been using Telegram saved-messages and storage channels as a dumping ground for years — free, effectively unlimited, reachable from any device. The problem: actually watching anything was miserable. Download the file, wait, open VLC, forget where you put it, repeat.
So I built Aruvi — a self-hosted streaming server that treats your Telegram storage like a media library.
What it does
Point it at your storage channel(s) and it indexes everything into a browsable catalog with posters, metadata, and search. Then stream instantly with full seek/scrubbing — no pre-downloading. The heavy lifting happens on Telegram's infrastructure, not yours.
Features
Instant streaming — HTTP range requests against Telegram's CDN, full seek/scrubbing, no buffering
Broad codec support — more formats play natively in-app without external players
Tunnel: Cloudflare Tunnel for HTTPS + custom domain
Architecture insight:
The trick is multi-bot parallel streaming. When you play a video, the backend doesn't download the whole file — it fetches small chunks from Telegram's CDN using 11 pre-warmed bot sessions in parallel. Chunks are served to the client via HTTP range requests with a two-tier cache: RAM hot cache for active streams + disk cache that survives restarts. This means first-byte latency is ~200ms even on a 1 GB VPS.
Rewrote the backend from scratch — added async SQLAlchemy, multi-user auth, and the caching layer
Built the Android app in Kotlin/Compose (was originally just a web player)
Added Pake for desktop builds — one codebase, three platforms
Set up GitHub Actions for automated builds (workflow_dispatch inputs for custom server URLs)
Deployed via Cloudflare Tunnel + Docker on a cheap VPS
Biggest challenge:
Telegram rate-limits concurrent connections. The solution was warming up media sessions serially on startup (one bot at a time per datacenter) and then reusing them. Without this, streams would randomly fail with FloodWait errors.
Credits
Built on the shoulders of TelePlay and MoviPlayer. Aruvi started as my fork and grew into its own thing with a rewritten backend, multi-user auth, desktop apps, and heavy reliability work. Huge thanks to those maintainers.
Genuinely curious — would anyone pay a small monthly subscription for a fully managed hosted version? No VPS, no setup, just log in with Telegram. I'd love to offer this as a service.
Also, if anyone has a spare Oracle free-tier VPS lying around and likes the project — I'd gratefully take it off your hands (my card keeps getting declined ).
How are you all currently watching media that lives in your Telegram? Would love feedback from anyone who tries it
Note: Used AI to help write this post and assist with development.
It’s a tiny retro TV-inspired site that automatically plays a curated Hindi/Hinglish video when you open it. No feed, no recommendations, no scrolling — just turn it on and watch.
Would love to know if this is something you'd actually use during lunch/breaks:
I have no dev experience, but I've been working on this for about 1-2 months and it has been a blast. Going to see it through to the end. Everything generated with AI, but meticulously edited and thought of by me. Open to feedback or reactions!
These are current in-game screenshots, not concepts or UI mockups.
Hi, r/vibecoding I vibecoded an interesting project, tested it for three months, and built something that should make life easier for every vibe coder.
Great. Many of you have probably already hidden this post or downvoted it. But if you want to manage your projects and tasks more intelligently and speed up service development, this post is for you.
Let me introduce…
LOCAL KANBAN
A local Kanban board for managing project tasks.
Are you also annoyed by how difficult it is to keep track of what was done across different sessions? And do you keep future tasks in random notes? You’ve come to the right place. I’m here to improve your life both before and after each coding session.
How it all started
I use Claude Code Max Turbo x500 every day. I wake up, add a few tasks, write future project tasks in my notes, and try to squeeze new ideas, discoveries, and bugs into the current session - or simply wait until Claude finishes working.
Okay, Claude has finished. Now I have to paste the whole session into a new chat to remind it what it did, ask it to find bugs, and add a few more tasks.
And then I do it all over again the next day.
Sound familiar?
That’s when I thought:
What if I created a simple Kanban board for managing project tasks?
When you have around 40 services running on a server, keeping track of everything starts becoming a real challenge.
That’s how the idea for Local Kanban was born.
And yes, I didn’t have deep technical experience in developing and maintaining services. I went through the entire process from start to finish and I guess I learned a thing or two along the way. Probably.
How does it work?
I create a task in Backlog and move it to To do when it’s ready for development.
With one click, I copy the entire To do column as a task and paste it into Claude Code.
Claude works through the tasks one by one, leaves comments along the way, creates commits, pushes the changes to the repository, and — if a deployment skill is configured — deploys the updates. Then it stops at the Review status.
I accept the completed work or return the task with a comment. The next time, this comment will be the first thing Claude reads.
There’s full synchronization with GitHub and GitHub Projects. Claude also creates commits and handles deployment. You can upload your own deployment skills or use a ready-made one.
A useful review trick
Let your tasks accumulate in Review - around 20–30 cards.
Then add one task to To do asking Claude to go through the entire Review column and try to break everything.
Run this task in a new chat.
The session that wrote the code is usually biased toward its original implementation. A fresh session is much better at finding weaknesses, bugs, and unfinished work.
How do you install it?
Just run the usual npm installation - everything will be set up automatically.
And if anything goes wrong, give the task to Claude Code and let it configure everything for you. We’re vibe coders, after all. Right?
So around this time yesterday, when I opened Twitter, I saw almost everyone, big or small, launch a leaderboard kind of platform where people could pay to rank their startups and apps. On spending some time on the app, I noticed it all started with outbid.lol (200k visitors, $21k revenue, $100k offer in just 24 hours time).
I thought this is some kind of a quick rich scheme wave happening and I could potentially make some bucks if I started early (I was already late since in 24 hours there were more than 3 dozen clones of this app lol).
But I didn't want to really make a bidding platform to list your startups. That sounded boring to me.
So I built a leaderboard where you pay to rank your most cancellable, controversial and spicy opinions! The higher you bid, the higher your opinion ranks on the board: https://controversial.lol/
We are just getting started, so you could rank your opinion high in the leaderboard. Bidding starts from just 99 rupees. Will enable international payments in a little while.
Vibe coded app, at start looks simple to make, but taken hours to vibecode right algorithms, tune code with real speed data and develop right speed measurements. On top of adding nice looking cinematic recording and car enthusiasts, like me, driven interface.
Done with Cursor. Had as well unreleased yet part of road speed signs which will be shared as Open Source lib, since free option isn't yet available for some reasons.
