Simply put, they set the bar too high for themselves

[sumaiyakhatun29]

Just to pass the lab, close the session. Switchers go through this path more compressed and often have no guidelines, what are the criteria for high-quality code, what are the priorities. A common trap at this stage is that switchers themselves come up with a level of understanding that they, having studied Java for three weeks, should understand it like enlightened people, and if they do not meet this level, they get upset, lose strength and hello procrastination.


Did not achieve it, and fell into depression. There is nothing wrong bolivia whatsapp fan with high standards if it stimulates them to move forward. If it deprives them of strength and leads to despondency, they need to change their approach. This is where typical problems arise: “they didn’t explain this to us, what are we being asked” (a school approach, not an engineering one), “there aren’t enough or few lectures, or they are not like that,” etc.


Although you need to be able to search for information. They didn’t explain it to everyone, but some are looking for solutions and find them, others are reasoning and complaining. A programmer at work: 30-40% reads the code, gets to the heart of the matter 40-50% googles, searches for info, studies, eliminates KNOWLEDGE GAPS 10-20% writes code. If theory is not enough, you need to add more.