← Back to context

Comment by aprilthird2021

20 hours ago

Be brave and post a GitHub of your code that you haven't written a lick of and haven't read.

EDIT: Come on? Won't post your code for everyone to see? Why not just put it all in a repo, client and server both?

EDIT 2: Amazing. If you punch in notes on the keyboard for like 10 seconds then click the keyboard-icon button on the bottom right the website crashes

EDIT 3: If you click the main CTA then click "Let's start" the website hangs and you need to manually refresh the page for the content to load

I could probably look over, and get some snippets, but currently only the client-side is live, so the code is sort of there, albeit I assume it's minified for production.

The game seems quite bug free though, including minigames. The UI could be better, but it's not done yet.

I do for example have an automated system that simulates progression, takes screenshots of the game to find potential hidden buttons or overlapping elements, to test for performance, etc.

If it looks like a duck, and quacks like a duck, I honestly don't see why I would review 100k's of lines of code.

EDIT: I might have replied in a wrong thread, but it was about this entirely "vibe-coded" app: https://game.ultimidi.com

  • That is an untested toy app that has no users.

    > why I would review 100k's of lines of code.

    If the core or that app is more than a few thousand lines of code, something is seriously wrong.

    I don’t want to shit on your app. It’s cool. I’m glad you built it. I’ve vibe coded all kinds of toy apps for myself and my kids.

    But it’s not strong evidence that code is irrelevant.

    • Thanks for your words.

      > If the core or that app is more than a few thousand lines of code, something is seriously wrong.

      That's the thing about vibe-coding: it is not the core, it is the entire app. We no longer make MVPs and release those, with AI we can make directly the app including all bells and whistles, entire progression, not just one level, all the systems around it.

      Why? Because if something needs changing, it's just one prompt away. I do think code is fluid now, any choice of architecture can be instantly changed at basically no cost.

      Maybe my mind is just finding ways to cope, thinking that I "wasted" thousands of solving coding challenges and fixing bugs, but I do think, for better or worse, that manually coding is gone. Same as we no longer code in assembly anymore. We no longer write C. We no longer write JavaScript. We no longer write TypeScript. Maybe not today, people don't like change, but manually writing or even viewing code will only be done in a few educational and high-performance/risk cases.

      8 replies →

Interesting, what browser are you using?

Also, what do you mean punch in notes? Like mashing keys and pressing 10 buttons at once?

Never had the app/website crash, tested only on Brave (desktop and mobile) so far.

  • Firefox Android

    • Thanks, only tested in webkit browsers, didn't know people use Firefox on mobile either.

      EDIT: I can reproduce the crashes, thanks, will tell the AI to test on Firefox too, testing on Firefox mobile specifically might be trickier to debug actually.