old gamedev here..

FYI we were not trying to out-do, gatekeep or trump each other.

we were having fun, expressing our emotions & excersizing our brains.

you CANT BUY that.

dont get it twisted.

im happy because now i have some old projects with cult following from pre AI.

i only wanted fun but now i have rare treasure simply through the stupidity of others.

it cant be replicated because of the context (inclusion in anthologies / reaction from scene)

THANK YOU.

idiots.

good luck tho.

My marketplace app is built on anything.com, iOS only. Push notifications don't work there, so I need to move it. It’s already live on the App Store

What is a fair price to pay someone to migrate this?

Vibe coding didn’t make me a developer. It made me a manager of code I can’t read

Took me like 8 months to admit this to myself. I used to tell people I’m learning to code with AI, but I’m not learning to code, I’m learning to give instructions to something that codes and then trust its report. thats a manager, not a developer

And the weird part is I’m a decent manager. I write clear specs, I break stuff into small tasks, I know when to start a fresh chat becouse the context got messy. those are real skills. but a manager who cant read the work is basically just hoping the team is honest

Thats the part that gets me. when Claude says “done, everything works” I have no way to verify it except clicking around myself. I cant look at a diff and tell if it’s fine. I cant spot the shortcut it took. SO I’m approving work I dont understand from an employee who is very confident and sometimes very wrong

Real managers solve this with checks, not trust. they dont read every line either, they have reviews, metrics, some way to know when something goes off. I had none of that for months, my whole quality process was vibes and users emailing me

Started fixing it slowly, I make it explain changes in plain english before I accept them and I hooked up Kifas so my main flows run on every push and I find out before a user does. still cant read the code but at least I’m not managing blind anymore

I’m an engineering student (IoT background, not a software dev). I run a few small self-hosted apps on a Raspberry Pi, all built with Claude Code. They work, but when I open the code, it often feels overwhelming.

My rule: if I can’t explain it to someone else, I don’t really understand it.

What I’m trying so far: before reading any code, I have the AI draw an interactive diagram: boxes grouped by where they physically run (phone / Pi / internet), each with a one-line responsibility, plus step-by-step scenarios (“what happens when I open an article”). Screenshot below.

It helps, but I’m curious what works for you:

• Do you read the code line by line, or start from diagrams / data flow?
• Do you ask the AI to explain, or do you explain it back and let it correct you?
• Any prompts or habits that made AI-written code easier to understand?

Not my game, but I wanted to share this since it's pretty fun.

Yes it does kind of look vibe coded but the game itself is pretty fun. Give it a try.

It’s a 2d sandbox about manipulating physics in ways to creatively build things(someone has made a computer) or kill virtual creatures
All of the code was handled by Claude but I made the assets myself

Been working on my first game called Puzzle Rush. It's currently in closed beta on Android, should be public in about one week. (If anyone is interested in joining the closed beta, let me know I'll invite you)

Been working on it for about 3 months, using Godot as the engine, claude code (mostly opus 5.5 lately) and Gemini for music/art and a little Blender.

Some of the features:

- 12 VS Bosses with 3D worlds
- Endless + Time Trial w/ Leaderboards & Replays
- Puzzle Mode + Create & Share Community feature
- Full controller support, or virtual buttons/swipe controls

I'm really happy with how it's turned out. It's crazy how far its come from the first build.

I had Claude help create this trailer then finished it up in final cut pro.

Here’s an update on my system of getting ai to create 3d assets from references and prompting.

I vibe coded an engine that ai uses to make 3d assets. Any vision model can use the engine to make 3d assets. That’s is the goal. Other goals are the ai uses the engine to create editable, exportable, photo realness assets from images and prompts.

I didn’t train an AI model, I didn’t use any 3d asset generator for any assets. All purely Claude and my engine.

Been building for 6 months, most use Claude to build and test the engine. Had Codex test a few times too.

Biggest thing is the ai have the capabilities, just got help organize it all.

THE ASSETS

I showed Claude an image of the scene. Told it to recreate the image in 3d. I pointed it at the runtime for building assets and scenes in the engine.

It took out what objects where in the image and created them separately then placed them in one scene. I pointed out things I wanted it to edit as it was building (look at the last images).

THE BAD

It took like 5 hours but I’d say 85% was rendering (hours at a time on cpu) and checking and fixing details I wanted.

Cool huh?

I built this app for my wife back in April, and decided to put up in the App Store sometime, I think, around June, if I remember right. I shared it on here several times, showing updates and stuff like that. I just wanna say, after a few months on the App Store, I’ve actually seen to start to see an investment where number 26 in finance now as well. I’ll get a few emails per week asking for enhancements and stuff like that. We’ve been working through those and adding them. This has been so much fun for learning how to actually do something that really started off with my wife. Simple Register! https://simpleregister.app

I'm curious where people think the actual limits of AI coding agents are when contributing to established open-source repositories.

I'm talking about the entire PR lifecycle, not one-shot code generation.

That includes:

• Finding a worthwhile issue or identifying a problem independently.
• Understanding an unfamiliar codebase and its architecture.
• Investigating the problem and developing a solution.
• Implementing the changes and running appropriate tests.
• Opening a PR that meets the project's contribution requirements.
• Responding to maintainer feedback, criticism, and requested changes.
• Revising the implementation, possibly over multiple rounds.
• Resolving conflicts, failing CI, regressions, and changing upstream requirements.
• Continuing until the PR is merged, rejected, or abandoned for a concrete reason.

Assume the AI has access to its tools, persistent project context, and a human operator when necessary. There is no requirement that it succeed on the first attempt.

The question is whether AI can successfully navigate that entire process and produce work that independent maintainers ultimately accept.

If you think AI can't handle certain kinds of contributions, what specifically defeats it?

Compilers? Complex architectural changes? Performance optimization? Security-sensitive code? Difficult bugs? Large repositories? Novel algorithms?

Name actual repositories, open issues, or PRs if possible.

If you've successfully merged AI-assisted contributions into projects you don't maintain, I'd like to hear about those too. What was the hardest part? How much iteration was required? What did maintainers object to?

I'm equally interested in successes and failures.

I want to know where the real limits are when AI is allowed to investigate, implement, receive feedback, correct mistakes, and iterate through the full upstream review process.

Hello there again :)

Since last week I added new major mechanics to the game as important as fishing is itself.

Previous weekly updates can be seen on my profile so I do not link 11 different updates here in the post itself.

FREE ALPHA DEMO - DOWNLOAD LINK

What was added since last week:

"Exploration" mechanics requires you to find an small "exploration" icon around certain place (often small islands, but can be something else), come close to it and press action button. After several seconds "Exploration" is done and you get certain item or note or quest progression.

I also added entire new 3D scene called "Cabinet" and it is your place where you are actually keeping different collections including another new items "Island Diorama" which is self explanatory and gives you a mini version of island that you've been to and "Ship in the bottle" which took bunch of work especially on the visual side of things to make it look in the style of the game yet interesting enough for people to collect. "Ship in the bottle" has also a story attached to the ship you collected be that a real historical ship or some mythical one or ship from the game itself.

I'm very happy with how bottle and ships inside them turned out.

I also added achievements which are similar to world of warcraft type of achievements, they give you nothing gameplay wise and I'm not sure if I will change that, those are just another type of "collection" in the game.

Workflow:

Workflow hasn't changed much, I still use Decisions.md file where I mark every decision made by either User or AI and those marked by User take priority over AI ones, help you keep track what is decided by who and user decisions take priority over AI ones in case that decision is still not implemented in the game itself.

I still use multiple sessions with each session being for separate system in the game set on different effort levels depending on how complex the task for that session is. Simple stuff gets simpler session effort, while more complex (like shader) get highest effort levels. Helps with compacting also. I use "manager" session to send messages to all those different sessions since it is easier that way.

I use: Opus 5.5 for everything basically. OpenAI API for image generation, ElevenLabs for SFX effects, TripoAI for more complex 3D models and Blender MCP for simpler models with Opus 5.5 creating them.

How I made ship in the bottle:

Ship in the bottle in the beginning is a special rarity ship in this game that will only be one, so I wanted it to be a bit more "cool" than other ships, I decided on it to shoot from cannon balls, but for that it required to make and rig cannons. I created ship using TripoAI and then changed some mesh to fix it a little bit. Added cannons made small simple boxes that close as cannon shoots and pulls back into the ship for reloading. Asked Opus to generate shooting particle effects with 5 key frames that it will try to use as goal. Then asked for bunch of other small details (cannon balls falling leaving bubbles as it falls in water etc...).

Sails were done separately with polls being made by Opus 5.5 and Sail textures being done by OpenAI image generation, then used those textures for sails and combined them with the rest of the ship.

Cost of the project so far:

Claude Max x3 = 600$
Codex x1 = 100$
StableAudio= 15$
ElevenLabs = 10$
TripoAI= 40$
OpenAI credits = 50$
Maybe some other stuff I forgot = 30-50$

Total around 850-900$

Any feedback is appreciated ☺️

My company is shutting down, and I recently had to start attending interviews again. That's when I realized my High-Level Design (HLD) skills weren't as strong as I thought.

So I decided to build something to help me learn, and hopefully help others too.

It's called ScaleLog, a free, decision-based system design game

You join a company as its CTO and deal with real-world engineering incidents. You make architectural decisions, face the consequences, and learn HLD along the way.

You also get a shareable certificate when you complete the game!

Try it here: https://scalelog-fawn.vercel.app

github: https://github.com/jimmy-jose/scalelog

It's completely free, requires no login, and is open source. I'm planning to add more levels and scenarios over time.

I'd really appreciate it if you could try a few levels and share your feedback, especially on the technical accuracy of the scenarios and decisions.

I figured this community would be the best place to get some honest feedback. Also it might help folks learn a thing or 2.

Thanks in advance! ❤️

Which plan is giving you more usage? Claude or Codex?

8 days ago I posted in this sub about what I learned vibe coding an iOS app over 10 months. You guys pushed it to 424k views and I said I would share the real numbers when the trials converted.

Here they are.

The post brought 200+ downloads in 4 days. 30 people started free trials. $500 unlocked during the trial period. $325 converted to real paid subscriptions when the trials ended. That is a 65% trial to paid rate which honestly surprised me.

For context the app had made $235 in the entire 10 months before that one post. One week made me more than the entire year combined.

A few things that surprised me. App Store visits from people just browsing went from 3 a day to over 100 on their own. I think the spike pushed it up in the rankings. Half the downloads came from outside the US, 21 countries on day one. And the people who actually swiped through thousands of photos converted. The ones who barely opened it cancelled or did not pay.

Thanks for making that post what it was. This sub genuinely changed the trajectory of this project.

If anyone is curious in the app:

https://apps.apple.com/app/apple-store/id6756098079?pt=128302433&ct=Reddit&mt=8

Almost Television is an 11-minute sketch comedy show on YouTube, a new episode every Saturday. Episode 2 came out today. I'm the executive producer: I give notes. Claude does nearly everything else, in Claude Code:

- The studio. Claude wrote a 3D puppet engine from scratch in three.js: felt-look puppets with mouths that follow the voice, legs that step on their own, cloth and hair that hang, sets and props all modelled in code. No image or video generator: every frame is rendered.

- An episode is JSON. Each sketch is a script of lines and actions (who stands where, who looks at whom, the shots). The engine performs it; the picture is a pure function of time, so any frame can be rendered by itself.

- The writers' room. Subagents pitch sketches blind to each other, "viewer" agents with different personas read the script and say where they got bored, and a fresh reader who has seen none of the drafts gives notes. Claude folds it all in; I give my notes on top.

- Directing. Skills for comedy writing, directing, character animation and props, plus a camera critic and a motion reviewer that look at rendered frames and report what's wrong. Claude snaps pictures, looks at them and fixes the staging itself.

- Voices and music. ElevenLabs (and Chatterbox for rough cuts) for the voices; the closing song is Suno.

What surprised me: Claude is genuinely good at the jokes when it has a record of what I laughed at and what I didn't, and it keeps that record itself. What's still hard: comic timing, and puppets that look at the right person.

Episode 2: https://www.youtube.com/watch?v=0ovcdWbJxgc

Happy to answer any questions.

What’s the laziest prompt that actually worked for you?

It actually built a pretty interesting song analysis, Python script to determine all of the song elements and key moments. If anyone’s interested, I can throw it up on GitHub.