Hello, I would like to listen to a lot of tips on how to best master programming. As some advise reading books and making small examples, while others advise you to start writing a large project and learn what you need and how to implement it. I write on the pros.

Closed due to the fact that off-topic participants Nick Volynkin ♦ , torokhkun , Streletz , Vlad , user194374 Dec 1 '15 at 7:41 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • " Questionnaires are forbidden on Stack Overflow in Russian . To get an answer, rephrase your question so that it can be given an unambiguously correct answer." - Streletz, Vlad, Community Spirit
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • Begin to do at least something, and not think. - moron
  • I do it this way, I made at least 400 small tasks in 100 - 400 lines, but it seems to be missing something. - Artie Lay

3 answers 3

My opinion is: first books and solve examples of them. Then write small utilities. Then necessarily a large project, otherwise you will never understand why classes are needed.

In addition, it makes sense to participate in projects like Hashcode or StackOverflow: answering the questions of others you can learn a lot yourself, because to give a good answer, you have to figure it out yourself.

C ++ may not be the best first language, it is redundantly complex and not always logical for backward compatibility. I would recommend either pure C, or Python, or both. If you can program and just want to learn C ++, then, of course, you need C ++.

  • It is rather the first language I took seriously, first I had Pascal, sometimes C #, but C ++ hooked and I don’t want to retreat, I understand how complicated it is, but the complexity does not scare me. - Artie Lay
  • Then good luck! - VladD
  • While reading, I understand everything, sometimes it happens that I read it, I think that I did not understand it, and after a week I calmly and happily perform this task without any repetitions. - Artie Lay
  • one
    For small tasks, essentially, neither classes, nor patterns, nor exceptions, nor any well-thought-out architecture are needed. But on small tasks the “small technique” is well honed - the ability to write code correctly, clearly and compactly. - VladD
  • one
    Yeah, small. How many classes do you have in the project? If less than 10, the project is small. There are hundreds of classes in a big project. - VladD

Come up with an idea like "I want to write this." And start writing. As write for yourself, there will be interest. In the course of developing such “applications for oneself”, it is the understanding of what-where-why.

But after learning from such an example, after some time, if you open the code of this application, you will find many things that can be improved-accelerated- (remove that horror). This shows progress.

An example from life, so he studied from scratch.

  • But before that, you first learned the syntax and capabilities superficially? - Artie Lay
  • one
    @Artemiy_plus_plus, at the level of understanding what #include is, that is, well, quite superficially. - Max Zhukov
  • five
    And there is. If a person his own code two years ago does not seem bad, he does not grow above himself. - VladD

Dare, do, help others

  • Well, you are pessimistic somehow :-) - VladD
  • @VladD, the first 4 frames are quite (and seriously) true :) - zhecky
  • one
    Well, I'm stuck on the third, and I understand that I'm in the right direction) - Artie Lay
  • If you feel stuck on trifles, then try something bigger. - avp pm