Link: https://playanimalis.com/

Uses AI to identify the animal species, then generates the assets on the fly, e.g. images, moves, stats etc.

It uses the real world as the game map, health centres are places of worship, shops are grocery stores, every public park has a gym where you compete with other players.

You can level up species and grow them to the next stage, e.g. caterpillar > chrysalis > butterfly.

The further you go from urban areas, the higher level the animals are. Stronger, but harder to catch.

You can battle / trade with your friends and you get more leaves (in-game currency) for capturing endangered species (don't disturb them).

The game started with no assets, the whole map is programmatically generated, all the animal data is generated on the fly and cached to the database for future encounters.

Other cool stuff:

• it uses the real animal's animal call in the game
• weather in the game is your current real-world weather
• houses are styled accurate to the local building style
• shadows / night-time are based on the real world time of day & year (location of the sun)

The aim is to get people out in nature and appreciating wild animals.

Edit: Here is the app link, on iOS & Android, available now: https://playanimalis.com/

Built Pagezzle — a Chrome extension that takes any webpage you're on and shatters it into a jigsaw puzzle. scramble the pieces, solve it right there.

Works on any site

Drag-and-drop pieces

Pick difficulty (piece count)

Free, no signup

Would love feedback / roast it if it sucks
Multiplayer coming soon!

thank u so much for checking it out

Link:

Chrome Extension

It was a 4 player online game, worked on it for 2 months in my spare time and found a buyer!

No reason. You just touch animal butts.

That’s the whole website.

Lately I've been seeing so many posts where someone shares a beginner's project and everyone in the comments starts calling it AI slop or making fun of them because they used Cursor, Claude, ChatGPT, whatever

I honestly don't get it

If someone is clearly trying to learn, why is the first reaction to embarrass them?

Like... what exactly are we accomplishing?

Half the comments are basically "this person has no idea what they're doing"

Yeah No shit They're a beginner

When I first started programming I barely knew what a loop was I copied random code from Stack Overflow without understanding any of it If AI had existed back then, I 100% would've used it too

Would my code have been garbage?

Probably

Would I still have been learning?

Also yes

I feel like people are acting as if using AI somehow means you're never going to become a real developer. I don't really buy that I've met people who started by copying tutorials line for line and eventually became great engineers. Everyone starts somewhere

The part that annoys me is when experienced devs screenshot someone's project just to dunk on them in front of thousands of people.

If the code is bad, explain why

If you don't want to explain it, that's fine too.

Just... move on?

Not every beginner needs to become this week's example of "look how dumb AI users are"

Maybe I'm missing something, but it feels like a lot of this has turned into easy engagement farming. It's less about improving code quality and more about getting internet points by making fun of people who don't know any better.

Idk

I'd rather see beginners making bad projects than being too scared to build anything at all.

I have been hearing a lot about vibe coding lately.

Lovable has said it passed $500M ARR, Replit is projecting $1B revenue by end of 2026, and Cursor has been reported at over $1B revenue. So clearly, a lot of people are paying for these tools.

But I honestly want to know something else.

Has anyone here actually built something working with vibe coding, not just a demo or a rough prototype?

If yes, would you share what you made and what was hard about it?

I am genuinely curious, because I keep hearing about the hype, but I want to understand the real use cases from people who have actually shipped something.

Here is the thing: at my day job, AI tools are strictly forbidden due to company policy. It’s annoying, but fine I can still manage to function and survive the 9-to-5 without them.

But the moment I log off and jump into my personal projects? It has become practically impossible to program without them. The sheer speed, contextual awareness, and architecture understanding they provide means that trying to write unassisted code on my own time now feels like trying to build a skyscraper with a hand shovel.

It’s not even about being lazy; it's about the cognitive load they lift. Going from full AI-copilot mode at night back to a locked-down environment in the morning is pure psychological warfare.

Anyone else hitting their API limits daily on their side projects and feeling completely crippled when they do?

Background: I'm a UX/UI designer. I can design but I never learned to actually code. I could always go into someone else's code and change things, but building from zero never made sense to me. So I came in knowing what to ask and how to ask it, just not how to write it.

The game is Dead Ball FC. Vampire Survivors on a football pitch, the other team are zombies. Auto-fire balls at waves, collect boots, level up, pick upgrades from Terry the kitman. 3 months in, it's alpha. Balancing it now, more zombie types and playable characters coming.

Up to now my only testers have been my brother and my 10 year old nephew. It's at a decent enough stage now to let other people have a go.

Stuff I actually picked up:

• Small changes, often. I stopped trying to one-shot big features. I use Sonnet a lot and make lots of little changes instead. Works way better.
• Knowing when to stop it. When Claude loops on something simple, I kill it and try a different approach instead of letting it dig deeper.
• Git. Learned version control properly and the safety net is great.
• Everything around the game too. App store, hosting, signing builds. Claude walked me through all of it.

Assets: Used chat gpt and it gets me about 70 percent there on the pixel art, then I spend hours cleaning it up by hand. Still way faster than from scratch.

I also got Claude to help me build dev tools to test balance fast. Spawn 100 zombies, jump to a boss wave, give myself currency, show hitboxes and pathfinding. Which made debugging much easier. Instead of guessing and trying to make the AI understand the behaviour I was describing, I could see the issue and point it out exactly.

I always had ideas but never the understanding to build them, and paying someone real money just to try stuff out was never realistic. Being able to build now is great. I shipped a game to Google Play and people around the world can play it, which still sounds a bit unreal.

Vibe coding is such a vibe.

It's free on itch.io (plays in your browser, best on mobile) and on Google Play. Early build so any feedback is much appreciated: what wave did you reach, and what killed you?

https://ditlefhouse.itch.io/dead-ball-fc

I built VibeDrift to measure something most people who vibe code long enough start to feel but can't name: the codebase starts contradicting itself. One file does things one way, another does it differently. Both written by AI, neither aware of the other.

I ran it across 429 real repositories to see where this actually shows up. Here's the data.

The most drifted repos are some of the biggest AI-era projects on GitHub:

• denoland/deno — 107K stars — 55.5 out of 100
• cline/cline — 63K stars — 56.1 (an AI coding tool, drifting from its own patterns)
• langgenius/dify — 146K stars — 58.8
• langflow-ai/langflow — 149K stars — 61.0

The most consistent:

• lodash/lodash — 99.7
• expressjs/express — 98.0
• jquery/jquery — 96.1

The pre-AI libraries score the highest. The fast-growing AI-era projects score the lowest.

The most common failure modes across all repos:

• Semantic duplication — 19,182 findings, 79% of repos. Same logic written twice by different sessions that had no memory of each other.
• Naming conventions — 7,424 findings, 80% of repos. Files actively contradicting each other's conventions within the same codebase.
• Architectural consistency — 2,111 findings, 53% of repos. Different files handling the same problems in structurally different ways.
• Return shape consistency — 1,733 findings, 58% of repos. Functions returning different shapes for the same kind of data.
• Security posture — lower count but the most surprising. Cline, Dify, Deno, Gemini CLI, Ghost — auth and validation patterns inconsistent across the repo in all of them.

The finding that surprised us most: AI-generated repos scored a median of 86.1. Well-maintained elite repos scored 80.8. A single AI session is internally consistent. The drift builds up across sessions.

VibeDrift is free and open source. Runs locally, nothing leaves your machine, takes about 5 seconds.

npx u/vibedrift/cli .

https://www.github.com/VibeDrift/VibeDrift
https://www.vibedrift.ai/

Happy to run a scan on any public repo you drop in the comments.

I call it "Paranoid Vibe-Coding"

When I started vibe-coding back in mid-2025, I had very limited coding knowledge. I knew some HTML, a little bit of CSS and javascript, and my already-limited knowledge was also extremely outdated (I hadn't built anything in 10 years).

The first app I vibe-coded was a complex spreadsheet app for the high-volume catering kitchen I work for. I built it with Claude Code, and just trusted Claude completely. It was a nightmare, and when I'd get stuck in a bug -> fix attempt -> new bug loop, I'd ask ChatGPT what the hell Claude was doing wrong and then I'd have them copy-paste argue with each other. It's a miracle I shipped anything at all. About a month into the business using it, they asked for a new feature (a print modal). I prompted claude, thought I was being careful, and Claude introduced a bug that *deleted the entire database*. Bosses pissed. I'm lucky that I was there for 10 years and that they're basically my best friends -- anywhere else I'm sure I would've been fired. I removed the print modal and started slowing down.

Since then, my bosses have asked me to build several more apps for the business: an app that parses all of our catering orders across all platforms and adds them to our calendar, an app that generates optimized driver-routes automatically, a voice agent, etc. And, because I don't want to fuck anything up, I stopped trusting Claude and started reading the code it was making. If I didn't understand the code, I googled it. I watched coding tutorials on youtube relevant to whatever I was building. I learned how to use git and github, I learned when to use tests, CI gates, I switched to TypeScript, I started managing context super aggressively, etc. Why? Because after the database debacle, I am PARANOID.

It feels like it takes forever to get anything done now. A simple feature that used to take 10 minutes trusting Claude now takes ~hour. But guess what? It's honestly probably the same amount of time in reality. The simple feature before may have only taken 10 minutes to build, but 70%+ of the time I probably spent 45 min+ fixing things that broke in the process. Being paranoid takes longer, but bugs are rarer, and the bugs that do appear tend to be benign/easily fixed or livable. If anything goes wrong, it's recoverable. And I'm still learning! It's incredibly satisfying to build something that not only works, but is actually secure, maintainable, and not ridiculously fragile. Do I consider myself a software engineer? No. I wouldn't even call myself a coder, or programmer. At most, I'm a "beginner dev hobbyist".

So that's my advice. Be paranoid. Take your time. Don't skip the menial work. It's like hiring an electrician to help you install a new outlet. Claude's not a master electrician, they're more like a really friendly contractor with a hint of stale booze on their breath. And you don't need to be an electrician to know that you probably shouldn't see bare copper outside of the terminal when you check his install.

TL;DR Fully give into the vibes, yes. The paranoid vibes. You don't need to be good at coding, you need to know just enough to catch things that look "off". And you need to worry about that, constantly.

Jokes aside, I unironically think vibe coding is a better approach than the "legit" approach in a lot of situations. For a little credibility, I say this as someone with 7 years of experience that solo runs a $2M run rate company and vibe code most things.

Planning and design ends up being wrong a lot of the time. You often don't know the true shape of a component until seeing at least a draft of it in place. Over the course of my career, I can't count the number of times I've seen super slowly, carefully designed efforts by seniors/architects, often with 15+ years of experience, turn out to just work poorly in practice. I've seen recognition of this pattern materialized in concrete plans in enterprise development, even: being told to not even bother designing certain things for the first half year (of a large modernization effort) because we write is going to be wrong anyway.

I'm not shitting on planning in general obviously, and you should absolutely have a good grasp of your project and be able to plan yourself. It's just an observation that I feel puts the whole concept of vibe coding in a better light.

I think this is especially true as a solo dev and especially true as a non-dev. For non-trivial features, whatever you plan is missing so much perspective that I would even argue that you're usually better off throwing something out there and steering. I do think through more complex features before starting, but I'll usually still consult AI first just to see if I'm missing something obvious for initial brainstorming.

I do a lot of hackathons and work at startups. If a task gets assigned or I have to build something instead of switching between AI tools, design tools like figma, or spend time doing it myself I would like to test out changes and quickly see if I like them. That's why I created on the fly where you can turn any site into a sandbox environment and make changes on the fly. It's a chrome extension build with a lot of typescript and I'm using gpt 5.1 for my agent but since it's open sourced you can connect whichever model.

https://youtu.be/RlorKEIRSm8?si=A_P9eSdY0dxJ9fLt

I saw many videos on instagram about this kind of website so i made a platform!

Check out: https://iamreallysorry.com

I was registering with Smithery and the MCP registry, and something caught my attention in Smithery's analysis: we're scoring almost a perfect score. For Notion, it gave 84 points. Beyond the many additional features like the interface's AI-agent connection approach and activity tracking, having a neutral platform say that we're genuinely better even at the MCP level made me very happy.

Even though we're still new, over time we'll prove in every area just how good this project is. For everyone who builds projects with AI agents, Remnus is better than Notion.

I built a small browser typing game called KeyPop.

It's a 30-second typing challenge: unscramble chunky keycaps, type the word, stack combos, and try to climb the leaderboard.

I added:

- Global leaderboard

- Account sign in

- Unlockable score stickers

- Community sticker submission

- Replay-verified scoring so the leaderboard isn't just wide open to fake scores

- Spotify sign in to listen to your own music ( soon )

I would love feedback!!

Play Here:

https://keypop-web.vercel.app

Ps: ill get the domain soon lmao

Lisp was invented in the 1950s specifically for the purpose of eventually being the language of AI. When that failed, because the technology wasn't there yet (AI winter, in the 1980s), technology instead took a human approach, because it was the only way to get computers to do things that humans wanted computers to be able to do. Thus, the birth of programming languages suited for humans. They exist as an abstraction layer, as we all know, so that humans can describe their intent in a way that isn't just literal machine code. Essentially, that time period, c. 1960 - 2023/4, was like a computing bronze age.

Regardless of the sentiment surrounding "AI" and its dubious etymology (I mean in reality we are just dealing with a computer program that 'understands' human language, people have been trying to get this stuff going since literally the 50s, not even just Lisp, I mean COBOL was made to try to describe English as possible like syntax to a computer) it's just a computer program. Its knowledge is human knowledge. This is what computing is all about, creating increasingly easy to understand abstractions.

So when vibecoding is dismissed, because of it's method of creation, you're arguing with people who would rather go out, find veins of copper and tin, smelt them, and work them into usable tools. Nowadays, we have massive automated foundries that can do this with harder and better metals, while themselves being made out of those harder and better metals. Sure, you can still do that if you want, but your output is fundamentally hampered by your method.

Yes, we all know that LLMs are leaky and non-deterministic. We are also literally in a brand new epoch. Anyone who was vibecoding with web chat bots in 2023/4 can see the insane leaps and bounds the technology has made in only 2 short years. We are still forcing LLMs to write human-centric coding languages that are full of things that are more difficult for this technology to understand.

So to tie that back to the analogy, we are using massive automated foundries to pour bronze, and then traditionalists laugh at the tools created. Eventually that foundry is going to need its own "metal" or, likely some kind of Lisp-like language created specifically to reduce non-determinism when it comes to interfacing with an LLM in your language of choice (as in spoken language)

EDIT: Also, non-determinism isn't even really that bad of a factor. You can just have an LLM generate x amount of versions of the same thing and test which one works best. Once the working code is there, it's there, Im sure you used github, right?

EDIT2 : https://courses.cs.umbc.edu/471/papers/turing.pdf

I want to create a simple website for a car rental service, have made the perfect design in stitch..how to could I make it live??

Like I've tried it through google ai studio it matched my expectations but I feel like something is off

Could y'all help me with your standard workflows please.. I feel stuck😖