How to escape when vibe coding goes wrong
by•
Keep all possibilities open — Don't trust AI guessing. Make it verify with actual server, DB, API calls
Read the functions your function calls — Don't guess, actually trace the logic. Timing conflicts between functions cause one to get skipped
Search everywhere that function is used — It's being called somewhere you didn't expect
Fixed a screen freeze bug that wouldn't go away for days using this method. The culprit was insufficient function call intervals + fit function not executing.https://www.solhun.com/changelog
Sharing the actual prompt in the comments.
54 views
Replies
I love this reminder. I've learned that when something freezes, it's rarely magic, it's skipped execution or race conditions. Tracing real calls instead of guessing has saved my sanity more than once.
CLI Manager
Follow these rules when debugging:
- No guessing. Log server responses and DB query results directly. Call APIs yourself to verify actual return values
- Find every function that the problem function calls, actually read them, and trace the logic
- Check for timing conflicts between functions. See if one hasn't finished before the next one runs - Search the entire project for everywhere this function is called and verify each one has no issues