How to understand what and how to google for a beginner when learning programming from scratch?

Question

IT education

Hello!

I want to ask people who have been working as programmers for more than a year, in any of the programming languages!

After watching a couple of videos and reading several articles about "How to write programs, project creation stages, development stages" I understood the following:

1. Understand the problem, what the program does, what is the input and output, how the user sees the program
2. Formulation requirements for the program from a fictitious "CUSTOMER"
3. Construction of the project architecture (UML, pseudocode)
4. Decomposition
5. We start programming piece by piece and assemble the puzzle guided by the UML architecture of the project
6. We write tests

and the idea of ​​​​how to do this or at least something similar, for example, there are tic-tac-toe, there is chess, there is tetris, there is sudoku, and now I understand by googling how to fill the field with arrays, how to make a snake or sudoku! Is it true that you need to google to set tasks and try to solve the problem, but before that, think for yourself but to a reasonable extent ???
It was the case that in chapters 2-3 of the Head first java textbook, I spent 5 hours to complete the "Puzzle by the pool" exercises, who knows, there an additional task was to display another number and this could only be done knowing that the object assigned with the equal sign did not become copy and just 2 references to 1 object and without googling the comment on the forum, I would not understand that the cat1.age + cat2.age variables, provided that cat1 = cat2 will refer to one object and their variables will be one for 2 instances of the class!

How to google and program wisely, where is the border that it's time to ask Google or YouTube "Google how to ... do it?"

Thank you all for your attention and help!!!

Answer 1

The demonstrated approach is to make a dump in the head.
Nothing can be learned this way, and programming is no exception.
Pick up a beginner-friendly book and read consistently while doing the exercises.

Answer 2

Until you have experience in solving banal tasks, you will not be able to start fulfilling your 6 points.
Reduce the task to that piece of an elephant that you can actually swallow, and when it is embodied in code - only then try to grab onto the next one.
Can't imagine all the interconnections in chess? Put aside chess, make a Sudoku and a snake, but not approximately, but in such a way that it works. Then take on tasks in which you can already solve this banal part, this will simplify the solution of the rest.
That you can, after reading a textbook on the grammar of a language, build a workable class hierarchy - and do not hope. The rake is waiting. But googling and asking at crossroads is useless. Himself - with a nose in sawdust, as the Pencil used to say.

Answer 3

Books are good, but then. A programmer with 7 years of experience - that's a lot later!
I also wanted to study books, but here I was advised to take a course on stepik.org. And this is very good advice! There are exercises in the books, but this is not the same. The course is a dosed theory + MANY tasks. Those. each topic you consider in practice repeatedly and from different angles. Your solution is checked by the test system, you can discuss it with other participants in the comments.
You learn to disassemble problems - from simple to more complex. On the course, they don’t give you the whole theory - you have to look for a lot yourself, and this is also right.
As a result, you have a hand full of:
- understanding of the task;
- drawing up an algorithm;
- writing it in the form of a code;
- debugging the program - this is extremely important!
- search for the necessary on the Internet;
- using an IDE.
After that, you can read books. They will fill in the blanks: "Wow, I use this, but it turns out that's it!". You will understand what you read. you already know many things, and you also know how things work that you don’t know yet.
And you need to communicate with a programmer later - when your brain is rebuilt and you start communicating in the same language :)

Answer 4

If it is difficult to make chess, first write helloworld and
then complicate
the Array, this is correct, you just have a misunderstanding that an array with data on figures and a visual picture are different things.