My First Few Months as a Junior Front End Web Developer

In April 2016, I was successful in gaining my first position as an in-house Front End Web Developer. I spent around 2 months looking for a role, and was super excited when I found out that I have been offered a job due to interviewing well and showing initiative in my personal projects!

Fast forward to August 2016

The first few months have been a huge learning curve for me, so much so that it has been a blur. I have spent a fair amount of time learning the processes here and discovering just how my position fits in with the existing team.

We have a few projects running concurrently that are all interrelated with one another. It has taken me a while to really understand the position I am in, and to gain a clear perspective of how this business operates. As a developer, we need to understand:

  • What problems we are solving,
  • How we are solving them,
  • Why we are solving them,
  • And the impact of the work we are doing.

In addition to getting up to speed with the technologies that we work with.

My experience here has been priceless due to being exposed to and sharing knowledge with more experienced developers. I have learned a plethora of technical knowledge in web development and gain confidence daily as I understand more.

I’d like to share a few of my experiences during this career change..

The best thing is…

...that you know you will start your career in tech knowing that you do not know a lot. This is a source of stress at times, however, you can reduce this if you are able to relax a little and become a sponge to your environment. In essence, you have less responsibilities so just relax and learn!

The next best thing is…

...you will meet and work with some interesting people.

My colleagues regularly provide me with illuminating experiences with their expertise. I tend to ask questions that draw out the experiences of my colleagues to try to understand what is to be expected in this career. I am fortunate enough to speak with a mix of people in different roles, and different terms of employment (permanent or contractors) which has helped me to grasp a solid overview of our industry.

The least expected thing is…

...that you will start seeing patterns in code. Moreover, you will start to realise that there are multiple ways to solve a problem through code. Code efficiency will become your goal.

The most surprising thing is…

...you’ll start to develop an intuition when you look at code regularly. When I have written some code, I feel that it usually isn’t the most efficient way to solve a problem. I’ll usually as one of my colleagues who will challenge me by asking “Why have you written it this way?”. We discuss and come up with a better solution.

The hardest thing is...

...thinking like a developer. A combination of Known Unknowns (the dictionary definition of the word 'ignorance', and not out of ego) and Unknown Unknowns (nescience) can become frustrating. It is natural to be frustrated when you are inexperienced and don’t know how to solve a problem, or when you don’t know how to explain an error to your colleagues.

I guess that this is a reason why most developers are pretty humble as they have already experienced what I am going through.

I'm keeping this one short as I’ll be writing a more technical blog post within the coming weeks, but if you want to know info in the meantime, get in touch!

Also, there will be an huge overhaul of this site within the next month or so. I am excited with the design of the site, and it will be the best of my work in my progression as a Front-End Web Developer.

Until then...keep pushin'!