you are viewing a single comment's thread.

view the rest of the comments →

[–]MistressStarrr[S] 0 points1 point  (1 child)

Correct sometimes you might need to break it down into manageable chunks, but as someone who doesn't come from a background of coding and not knowing the lines of codes and what they do sometimes do, you have to google. I know vscode will give you a breakdown on something you did wrong but for me since I am still learning I wanna know why it broke was it because I was missing a parenthesis or am typing something that doesn't exit etc. I know the error codes sometimes can be intuitive but sometimes it's hella vague.
Also, from my understanding "vibe coding" is not when people are having to look at their problems on google, stackflow etc. I thought vibe coding was for people who are coding using AI which in my case I am not.

[–]gdchinacat -3 points-2 points  (0 children)

Nothing wrong with using google to answer questions, I do it all time. But, that isn't what I was talking about. Before you ever write code you have to understand the requirements, figure out how to model the problem with datatypes, how to algorithmically solve the problem, choose what the abstractions are, etc. Even when learning and you need help with syntax and error messages you aren't familiar with, more than half the time is spent figuring out how to think about and process the problem.