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!
Google "how often should software engineers switch jobs" and you'll find that 3 years is the sweet spot. Personally, I don't believe in such rigid rules, but most developers will eventually feel the urge to put their talent and skills to the test elsewhere.
So, what to do when you get to this point?
As a software engineer who has recently landed a new job, I'm coming with a wide range of handy tips on career moves.
It happens that software developers focus too much on completing tasks and watching them move across Scrum boards instead of thinking what good their code might bring.
If you understand the needs driving the requirements, you will write better code. All the change requests coming your way will make more sense. When things make sense to you, it is less frustrating to change the same code again and again. But most of all, you give yourself a chance for a little oxytocin. Your body releases it as a reaction to positive social interactions. It is the feeling you get when you are glad that you were able to help someone.
Knowing these dependencies, it’s only natural to try to develop empathy before you develop software. It’s a win-win situation!
New in the IT industry? Looking for the next job in tech? Either way, this beginner’s guide to IT employment will help you find a company you’ll love working for.
Learn what questions you should ask recruiters and how to verify your potential employer to make the best of your new career.
The early days of a new software project can be challenging.
There are a gazillion things to think of, and deciding where to start is a nerve-wracking moment.
No wonder you want to get past this phase as quickly as humanly possible.
Turns out it doesn’t get that much better towards the end either — applying application code changes requires a fair amount of time too.
Here are four simple steps to get around these bottlenecks and improve your software delivery performance.
According to CareerBuilder, nearly three in four employers have been affected by an unsuitable hire. Don’t let it happen to your organization. Make these 9 steps to find the right software engineer for your company.
