IT technologies are constantly changing and evolving. To keep up with this dynamic environment, software engineers must stay in the loop, keep growing, and take care of their mental state.
How to do so?
Here are eight tips to avoid stagnation and change specialization coming from an experienced Evojam backend developer.
For a long time, I believed that maths and programming are strongly interconnected and that learning programming requires a strictly scientific mind — something I didn’t have.
After graduating high school, I didn’t consider applying to any science majors, as I perceived them as incomprehensible and out of my reach. Computer Science was one of those majors hidden behind a wall I thought I couldn’t pass through.
That’s why I decided to go in a different direction — I chose an International Relations major with a specialisation focused on South-East Asia. I travelled a lot, learned Chinese, and had a lot of fun, but I didn’t know what career path I should follow after.
After some research and thought, I decided to apply for MA in Computer Science. It was a bold move — I was afraid I couldn’t make it, but I wanted to challenge myself and see if I found it fascinating.
I did, and I quickly landed my first job as a frontend developer. I was constantly learning more and more, and I soon graduated and found myself where I am now.
So, did my unscientific mind cause me any problems on the way?
Let this article be the answer!
As developers, we produce tons of code each day. We test our code, beautify it with code style scripts and finally verify using continuous integration commands, which control the integrity and cohesion of our solutions. Nevertheless, the true value of used code solution can be checked only by another developer, who knows the business domain, best practices, clean code principles and who may also have a different point of view from yours. In this article, I want to show you how code review can help you keep codebase in order and get more advantages for your team.