JuniorLearnsToCode

Change can seem difficult and scary, first day on a new job will always impact you emotionally, to a certain extent - even if you changed many jobs before. In this blog post I will share a few tips to help you make the transition easier and how to beat the fear of the unknown!  Keep Your Ego in Check Important thing is to be humble and kind, and leaving a good first impression (of course also make sure that the good first impression is also the lasting impression) as this will affect how people on your team perceive you. Don't be a cocky show-off, be polite and nice to everyone. Naturally this does not mean that you should put up with any abuse. Meet Everyone  Taking time to meet your new teammates is very important, and not just meeting them, getting to know them as individuals. People who are already working at your new workplace will be a lot more busy than you are so they might not initiate these kind of things, instead, you should be the one inviting people to lunch to ge...

This is not one of those yes or no questions, the answers is "it depends". The world is not black and white, one size does not fit all and as adults we often need to make trade-offs and compromises. In this blog post, I will try to list both pros and cons when it comes to working for smaller IT companies, compared to working for a larger IT company. You know, different strokes for different folks and all that. We all have rather unique needs and motivations and while one person might thrive in a more casual environment, that same atmosphere could hamper someone else's growth.  Working in a Small Company Since it is easier to manage a smaller number of people, there will be less management layers and generally, smaller companies have less official administrative procedures involved - for example, getting your vacation approved might be just a matter of checking with your team and updating the company's calendar. Another thing typical for smaller companies is that the p...

This is going to be a short post, as I just wanted to explain why you should not be intimidated by the official job requirements. I often notice that a lot of junior people complain about job postings, saying that job reequipments are too strict and that the list of required tools/technologies is too long. It is true that lot of jobs have inaccurate descriptions, as sometimes they are written by non-technical people and there can be a lot of copy/pasting involved, to include hot an trendy technologies, which my not even be used by the company that is posting the job! Another reason is filtering candidates by using a lot of "intimidating" buzzwords, this way company scare of many enter level applicants as they will give up without even trying. But let us look at this from a different angle. I have witnessed first hand that very often you will actually be working with just a small portion of tools mentioned in the official job posting. Many people I have talked to also confirme...

Various types of work attract different kinds of people, some of us like a dynamic work atmosphere, while others function best if things are more predictable and stable. Working for a big enterprise client is a lot different compared to dealing with clients directly while freelancing or working for a SaaS (Software as a service) in which case the company is it's own "client". I've worked in all three mentioned scenarios - currently, I'm working on a big enterprise project, in the past I've worked for several years for a company that was selling its own product and done some freelancing for a couple of years, as well. Bellow I will strive to list the advantages and disadvantages of all three types of jobs, in hope that this may prove useful for people looking for their first IT job. With memes, as always. So let's get started! Working for a SaaS Company Working for a SaaS, Software as a Service company, you usually won't have any interaction wit...