Chronology of programming knowledge, or how did you learn C++?

Question

Programming

The whole point, it seems to me, is already placed in the title. Here, I would like to see the chronology of language learning. What books did you read, what web resources did you use, etc. Only, preferably, write exactly the chronology , the study algorithm, so to speak.

Answer 1

1) Tried to learn C++.
2) I couldn’t
3) I scored
4) I learned Pascal, I understood what programming is
5) I tried to learn C
6) I was able to
7) I tried to learn C ++
8) I didn’t understand OOP, then it seemed that C ++ is only OOP, although it is possible in C (I still think so, I don’t see the advantages of C ++ over C, I would like to hear the advantages, thanks )
9) I learned about assembler
10) I learned assembler
11) I got tired of writing complex projects in RadAsm
12) I returned to C ++
13) I understood everything and learned
What I took the materials, I do not remember, I'm sorry.

Answer 2

Stroustrup -> Stroustrup -> Stroustrup.

Answer 3

C++ is impossible to learn, don't even try.
I have been teaching for 12 years.
1. Started with the book "Borland C++ 5.02" for dummies (my first programming book).
Thanks to her, I wrote two classes Foo and Bar. There was also a description of the GUI of the OWL library.
2. I read a lot rsdn.ru (now half-dead), borland.xportal.ru, absorbed it.
He almost never asked questions himself, because he knew how to use the search, and there were no problems with English. Answered the questions of others on various forums, helping others, gaining knowledge.
3. Started learning GUI application development in C++ Builder.
5. I read a lot of books. I don’t remember exactly the names, I liked the book, where practical advice and examples of the correct / incorrect use of C ++ were given, it seems "Effective use of C / C ++".
6. At school, in computer science lessons, I wrote the implementation of all sorts of linear lists/trees/calculations of integrals/derivatives/simple equations/minimum functions, however, in Pascal (we were forced to)
7. Learned to work with threads. Wrote a bunch of small projects for myself, mostly Winapi + WTL.
Tried to write C++ "games" on OpenGL/DirectX.
He wrote programs for himself and for others in C++ Builder, Delphi, Visual C++, C#, Java.
8. While still at school, I started writing an open-source project in C ++ (now there are about 70 thousand lines, partly cross-platform, I got acquainted with the features of different compilers). https://github.com/zenden2k/image-uploader . Wrote many other smaller projects.
9. Wrote labs/term papers/diploma in C++, C#, Java, Fortran, ASM, Bash, VHDL, Wolfram Mathematica, mssql at the university.
We had a C++ course lasting 2 semesters. We were forced to implement a standard container on our own (it seems std::vector). They also wrote some kind of database on text files with a gui interface.
Studied discrete/graph theory/matlogic/theory of compilers and formal languages. Wrote a simple recursive descent compiler in C++. Wrote the RTOS model in C++. Wrote some obscure queuing system (QS) first in Pascal, then in C++. Studied inter-thread synchronization using Winapi/Posix threads/java threads as an example.
10. Studied web programming, PHP, Javascript, mysql/postgres. Wrote a bunch of sites / web applications.
stackoverflow.com became my favorite site
11. I read the book "Perfect Code." - the kind still vodichka.
Studied the book "Thinking in Java" and C# by J. Richter. A good knowledge of other languages ​​will not hurt.
Discovered Google C++ Style Guide. I started to follow him.
But so far I can't say that I know C++ well enough. I guess I'm just a dumb, worthless programmer.
Template compilation errors, and especially linking errors, can make me freeze for a while. These errors are well "very informative". But thanks to experience and intuition, I cope with them, but for a beginner it will not be easy.

Answer 4

The first time I tried to write in C was in a programming course in the 9th grade. Then, in my first year at the institute, I bought the book Salter, Klepper "C ++ for professionals" (it's better not to start with it, of course) ... After I mastered C ++ at a sufficient level, I took up Qt, then boost (already purely for work). There were and are many different books (it is easy to google and search for the same toaster), articles, personal projects, etc.
As for the algorithm... You read, try an example, try it in some project. There is nothing more to add. Practice == successful learning. Well, you should not forget about knowledge in related areas. Operating systems, memory operation, design, etc. It is not enough just to know the syntax of the language, you need to be able to solve some practical tasks.

Answer 5

University-> Pascal-> c-> work at a university with a good mentor-> c ++ profit

Answer 6

C++ in 21 days. I already knew how to program, I knew OOP.
This book is now out of date.
But for a first language, this is a bad choice.

Answer 7

I needed a program, but I didn’t want to pay for its creation, so I had to google, read books, watch screencasts. I wrote the program, and away we go)

Answer 8

In my first year, I tried to learn C++ in parallel with Pascal. It didn't work, because there was a muddy manual and in working with memory, the approach of C (malloc) and C ++ (new - delete) was constantly mixed. Postponed
Course on the third read Podbelsky, skipping OOP (like taught C). Got an idea.
On the 5th course, I took control to order. It was here that I had to seriously delve into more modern and normal C ++ (I finally understood how links, memory management, inheritance, STL)
work. In short. If you don't get it right the first time, don't worry :) Sometimes you need to "mature mentally" to some things.
And Stroustrup as a textbook is absolutely not suitable. More like a book helping to put everything on the shelves, when you already know everything, but without a system.

Answer 9

At first I read a lot about him. Read source codes - examples in books. Then I started writing my project in c++/Qt. Then he got into a project that writes on it.