Is Monkeycoding Helpful or Harmful?

Question

Programming

It's just that, for example, I'm learning theory and monk coding for a friend, how? you just copy-paste the same frameworks from the docks and try to understand how and what) google all the time and that's it. True, I do not feel like a programmer, but a Googler.

Answer 1

It is necessary to conduct a retrospective analysis sometimes. Pokodil - think about what and why. I took it from the docks, think about why they did it that way

Answer 2

What do families and schools teach us?
That life itself will punish them severely.

Without being able to correctly build the architecture and work, you, of course, inevitably engage in decoy-coding. This is fine.
But you will accumulate so much technical debt in the shortest possible time that it will simply not work to resolve it without thinking. Willy-nilly, see your mistakes and reasons for doing smarter things that seemed logical to do quickly.
This is, of course, an optimistic scenario, but it's better to prepare for it than suck something out of your finger and think "how to program correctly" and not "how to refactor this particular cesspool now and never do it again."

Answer 3

everyone learns this way and almost everyone works this way, they just don’t admit it
in real projects and with real deadlines, otherwise it’s simply impossible to do anything

Answer 4

It seems to me that this is an integral part of the training, but, mind you, this is a PART OF THE TRAINING. People forget about it, and a person becomes a developer who codes, going to the Internet for every reason. It is not right. It is clear that it is difficult to remember or understand everything, there will always be problems, for the solution of which we climb into the Internet and forums.
Everything that you google, dig up, you use in your projects and must remember what you are doing, if, for example, you took animations in 2-3 lines from the Internet, then climbing back there for these two lines when you need them is bad decision. You should have memorized them right away. Because surfing the Internet takes N amount of time, and writing it out of your head N / 3 amount of time (we are talking about 2 lines of code).
If you are writing a complex project, then it is categorically useful for you to know what works and how it works (because you will support it with a 90% probability), so thoughtlessly copy-pasting pieces of code and not understanding them is stupidity, and copy-pasting what you already know makes sense , if your functionality is repeated exactly, that is, you would have written it out of your head, but we are lazy people, we take what we ourselves have already written.
Bottom line: such coding makes sense during training, because it allows you to quickly assimilate information in practice here and now, but using this method already during direct work is not the best quality for a developer.

Answer 5

Skopipasil - figure out why and how it works. You use the framework method - get into it and understand how it works.

Answer 6

At the initial stage, it is simply necessary, otherwise where will the stock of knowledge and visual habituation to the code / style be accumulated, at the stage of formation and self-development, you need to look and understand how and why a certain decision was made, at the growth stage we take someone else’s, look (and already see) that it is written crookedly in some places - we rule, we use it. We write a lot. Look like that's it.

Answer 7

Just don't copy-paste if you don't understand what each line of code does.