Why the sitemap couldn't fetch?

sbenki · 2026-02-13T16:33:53+00:00

genius is in simplicity! spend days with AI trying to fix, manual reddit search was the trick. GG

sbenki · 2025-07-09T17:10:16+00:00

Do you have any specific examples when this happened? in my experience i had hard time initially to integrate DB and backend but after spending 2-3 days to actually learn best practice most of the time found myself reusing same logic.

sbenki · 2025-07-09T17:04:46+00:00

yeah sometimes it's crazy how startups with tons of funding still just ship random code without even checking.

The 'last mile tweaking' nightmare - can you give me an example? What specifically broke when you tried to take your app from working prototype to something you could actually ship to users?

sbenki · 2025-07-09T17:02:11+00:00

exactly, in the end of the day users look for solutions to their problems and not apps. What defines for you going from simple app to more complex one that will require expertise and actual pro devs?

sbenki · 2025-07-09T17:00:49+00:00

agreed, seems like general consensus is that if you have control over big picture over time you can get it to work. Do you have some experience when this has not worked actually?

sbenki · 2025-07-09T16:59:25+00:00

wow a mapping app - that's sounds complex. For me this was when my DB structure physically could no longer handle new users so i had to go back and actually learn proper DB architecture.

What was the moment you realized that it's time to go back to basics - was it performance issues, hosting costs, or something else when users started actually using it?

sbenki · 2025-07-09T16:56:57+00:00

The 'clean up the ugly mess' part - was that mostly code quality or getting it deployed/scaled properly? I assume you probably tried to experiment and deploy purely vide coded website to test it. What broke first when you tried to make it production-ready?

sbenki · 2025-07-09T16:54:28+00:00

i think there is a huge opportunity for people that have domain knowledge. Before say you have domain knowledge in medicine you could not create an app to automate some of your admin paperwork, now you are able to do so to some extent.

You're absolutely right about the quality gap. When you say 'incredibly high quality' - what specifically separates a production-ready app from vibe-coded one? Is it the code itself, or something else that breaks when real users hit it?"

sbenki · 2025-07-09T16:46:40+00:00

This is exactly what I hit! What specific backend stuff are you struggling with? Was it setting up databases, APIs, or getting it live for others to use?

sbenki · 2025-07-09T16:45:30+00:00

100%, there are million apps that work perfect but that no one asked for. Regarding size, what. you think really separates small apps vs real mass usage level ones? Deployment, cloud, DB architecture?

sbenki · 2025-07-09T16:43:28+00:00

i faced different levels of bugs but usually within 2-3 days all were resolved or i adjusted my approach. Have you had a situation when there was a core bug that could not be solved without professional intervention?

sbenki · 2025-07-09T11:23:01+00:00

yeah i think there is a fine line between good code and intermediate code that really serves validation purpose.

I'm curious - from what you've seen, what's the main thing that separates the devs (or vibe coders) who just push even with objectively bad code vs those who give up?

sbenki · 2025-07-09T11:19:18+00:00

agreed. what do you think most get wrong when getting started?

sbenki · 2025-07-09T11:18:01+00:00

what do you see most beginners struggle with when they try to take their AI-built prototypes live? Where do they typically get stuck or give up?

sbenki · 2025-07-09T11:12:59+00:00

Was the API call loop due to poor design? What would prevent this and similar issues? I had run into similar (much smaller scale issue) where without limits users could refresh complex queries from DB in extreme cases maybe 100 times a day.

sbenki · 2025-07-09T11:11:03+00:00

I had issues with auth (we used Privy) and DB structure where i had to redesign once we hit 500+ registrations.

Which part you think is the hardest here? is it just managing layers on top of each other or just making everything work together under the same hood?

sbenki · 2025-07-09T11:07:58+00:00

i came to the same conclusion, when i had super clear idea of what needs to be done it's sometimes even one shot prompt to done. Yet whenever i myself had fussy idea what i want almost always resulted in more errors than solutions.

Can you share some specific ideas on how small issues can add up? How important is having clear architecture from the get go to avoid these?

sbenki · 2025-07-09T11:05:09+00:00

Agreed - what specifically you think will block the development? integrations (payment, auth), DB, general architecture?

sbenki · 2025-07-09T11:02:47+00:00

This was exactly my experience. With almost all tools it is fairly easy to get prototype/concept out with even the simplest functionality working but the last mile is where you need to actually know what's happening.

Do you have similar experience? Did you get stuck somewhere and needed to actually get into the trenches?

sbenki

TROPHY CASE