Frontend Developer Oleksandra Zubareva recalled the very beginning of her journey in frontend. She talked about the mistake she made then. Here’s what other IT professionals responded to her.
Frontend Developer Oleksandra Zubareva recalled the very beginning of her journey in frontend. She talked about the mistake she made then. Here’s what other IT professionals responded to her.
«When I was just starting my journey in frontend, it seemed to me that the more theory I learned, the better developer I would become,» said Oleksandra. Back then, she spent hours understanding the concepts of JavaScript, React, studying data structures, and the architecture of frontend applications.
She thought she knew a lot because she could talk about closures, execution context, or the component lifecycle. But, according to the developer, when it came to writing actual code, she didn’t know where to start.
«My mistake was that I put off practice „for later,“ afraid of doing something wrong,» Oleksandra explained.
This mistake taught the developer the main thing: «Theory doesn’t work without practice.»
Drawing on her own experience, Oleksandra changed her approach to learning new things. And the new attitude helped her not only understand technology more deeply, but also feel confident in her own abilities.
Now she immediately tries to apply the knowledge:
«If you’re just starting out, don’t be afraid to write code. Even small projects give more than dozens of articles read,» she advises other beginners.
Just do and practice is the golden rule for both the front and the back.
It’s similar, but I started out knowing HTML, and that’s just a drop in the ocean. It was a total shock to me how to combine these codes to make a Web application work!
It seems to me that this has happened to everyone, but now there is a problem when, you already have the skills, and you try to do everything perfectly, which can lead to the work being x2 in time. But your approach, which needs to be immediately put into practice, is super correct.
Well, it works the other way around too, practice without knowledge = bad code. Personally, I can say that it’s better to go and fix it all by hand when you’ve learned something.
I have the same errors.
- Firstly, without practice, everything is quickly forgotten.
- Secondly, you cannot take long pauses in learning and practice.
As Lao Tzu once said: «You cannot stop in Learning. To stop in Learning is to go backwards.»
Too much work — programming is addictive, similar to computer game addiction. You get positive reinforcement just as quickly
Lack of confidence in one’s abilities and knowledge!
Fear of mistakes and mega corrections.
Many people make another mistake: they ignore patterns, principles of good architecture and write to make it work, for POC the approach is normal, but on large projects this spaghetti code results in significant costs. So don’t think that your knowledge of the theory is an unnecessary burden. Knowing the banal event loop helps to avoid many mistakes.
The biggest mistake is to teach things you don’t need in pursuit of short-term goals.
