Being a junior has a lot to do with a state of mind. besides technical skills.
I want to tell you how I changed my “junior” state of mind and how I was able to give value much faster, which translates into a better salary, roles, and opportunities.
I will share practical tips that you can implement starting today.
If you haven’t read it yet, check out
It is important to remember that you are not your code.
It might seem a bit silly, but it is an easy mistake to fall into. We put so much thought and even creativity into our code, that it is only natural to become “defensive”.
Don’t get me wrong, we should know how to justify our decisions, but we should remember that in the end, the code is just a tool, and making mistakes or having room for improvement does not mean that WE are a failure.
Actually, being open to feedback and criticism is one of the best ways to learn new things and get a fresh perspective. We should thank other developers (and people in general) who put the time in order to give extensive feedback on our work.
I think that reminding myself that the code is not me, and all feedback is an opportunity to evolve and learn, even if I do not 100% agree, helped me to remain open to changes and to grow faster.
– – –
– – –
Who am I, and how did I end up here?
I am a software developer and Instructor with extensive experience leading both teams and projects, and over a decade teaching students and training staff.
A few years ago, Jonathan (Owner @Solvism) found me a job in a technical position after I moved to the Netherlands. He guided me through the Dutch working culture and got me a great fit. He did this in… wait for it… one day!
Since then we kept in touch, and when I had the opportunity to join the team and contribute with my knowledge and experience, I had to jump in! So here I am!