The story of how I changed my engineering major to IT. About two years ago, I decided to change my specialization and become a programmer. Before that, I worked as an engineer in a field unrelated to IT. From programming experience, I only had Paskal in my distant school past. A good starting advantage was knowing English at a fairly high level. On the advice of a friend, the choice of programming language immediately fell on Java, as the most popular one on the market at that time. I started by reading books and watching tutorials on YouTube. Then I accidentally came across the Javarush project and worked here for about six months (with breaks). In parallel with Javarush, I studied other topics/technologies of interest (such as SQL, HTML/CSS), and became familiar with the C++/C# syntax at a basic level. For my success on Javarush, the JR administration even gave me the opportunity to participate in the project for free (for which I am very grateful to them!), but, unfortunately, I could not maintain the pace of learning that Hubert set and was forced to leave the project. A little later, I enrolled in a programming course, where I studied for 5 months. There I became acquainted with the principles of building Java EE applications, a basic set of EE frameworks, and wrote my first project. At the same time, I polished my knowledge of various technologies on different resources and periodically “returned” to Javarush. Immediately after completing the courses, I started looking for a job (the search took six months, but that’s another long story :)). My IMHO about JavaRush: Pros : the main advantage for me initially was the presence of tasks - since for a novice programmer the problem is always “what to practice on.” Moreover, the quality of the tasks is quite high in terms of their technical versatility and diversity (I say this as a person who has worked on various resources). I also liked the lectures for their accessibility and content (if it were possible, I would continue reading lectures now). I liked that the theoretical material was immediately followed by practical implementation. A good selection of additional materials, from various sources, which is very cool for a beginner - you immediately discover many useful and informative resources. It was interesting to study, and overall I am pleased with the progress I made during my time here. Minuses: not a very convenient system for checking tasks without feedback. At first this was not particularly noticeable, but at higher levels I began to catch myself thinking that often 90% of the time solving a problem is spent not on drawing up a solution algorithm/studying the topic, but on trampling in circles: “which test case is failing my solution.” This became especially noticeable on large tasks. On the one hand, it seems like a challenge, but then you still realize that your time could be spent more usefully. I also didn’t like the fact that closer to level 30, in order to continue reading lectures, you need to solve almost all the problems without missing anything (coupled with the previous “problem”, because of this, the learning process slows down/stops greatly). Separately, I would like to highlight a real project - be sure to take part in it, the sooner the better. Learning Java Core is cool, but programmers are paid for their knowledge of Enterprise technologies. If you don’t want/can’t participate in a project on JR, look for other opportunities - programming courses or start writing something simple yourself (although it will be difficult at first without help). Here is my short history of learning, enjoy coding everyone :).
My IMHO about JavaRush: Pros : the main advantage for me initially was the presence of tasks - since for a novice programmer the problem is always “what to practice on.” Moreover, the quality of the tasks is quite high in terms of their technical versatility and diversity (I say this as a person who has worked on various resources). I also liked the lectures for their accessibility and content (if it were possible, I would continue reading lectures now). I liked that the theoretical material was immediately followed by practical implementation. A good selection of additional materials, from various sources, which is very cool for a beginner - you immediately discover many useful and informative resources. It was interesting to study, and overall I am pleased with the progress I made during my time here. Minuses: not a very convenient system for checking tasks without feedback. At first this was not particularly noticeable, but at higher levels I began to catch myself thinking that often 90% of the time solving a problem is spent not on drawing up a solution algorithm/studying the topic, but on trampling in circles: “which test case is failing my solution.” This became especially noticeable on large tasks. On the one hand, it seems like a challenge, but then you still realize that your time could be spent more usefully. I also didn’t like the fact that closer to level 30, in order to continue reading lectures, you need to solve almost all the problems without missing anything (coupled with the previous “problem”, because of this, the learning process slows down/stops greatly). Separately, I would like to highlight a real project - be sure to take part in it, the sooner the better. Learning Java Core is cool, but programmers are paid for their knowledge of Enterprise technologies. If you don’t want/can’t participate in a project on JR, look for other opportunities - programming courses or start writing something simple yourself (although it will be difficult at first without help). Here is my short history of learning, enjoy coding everyone :).
GO TO FULL VERSION