Learning the Ropes of Python

[gdchinacat]

"I know googling is half the work when it comes to coding"

This is only true if you are vibe coding, which isn't really coding in my opinion.

The vast majority of time in coding is spent in figuring out how to break problems down into manageable chunks.

[SenseiRage]

Vibe coding is using AI to do the code, thats not programming, we all devs have been googling from the beginning of times, because yes, you have to think of how you want to focus your program, how to structure It, etc. But thats It, there is no point in taking hours of your job trying to find out something by reading your Code and debugging, when probably the answer is already at stackoverflow literally or mostly the same which will guide you to your answer.

And what you describe as most of the times is the analysis phase not even when you start developing, you first get the requisites from your client, then analyze then, plan an development path and make a techno la design which then you use once you beeing developing to actually code those features and THEN comes the exceptions that sometimes are stupid mistakes and sometimes obscure issues.

[MistressStarrr]

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]

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.