MarcusOskarsson@hotmail.com

Am I good enough to get a junior developer role?

How do you know if / when you are a good enough developer to start working as one?

Status: Evergreen

Published on:

Last updated on:

TLDR: Perhaps, but maybe that is not the point. I believe I know what I excel at and what I need to work with some more. Until I get my first junior developer role and someone deems me qualified for the opportunity, I will continue working and try to feel good doing it.

Introduction: It has been almost two years since I decided to transition from librarian to developer. I read a lot about other experiences from being new in tech, about imposter syndrome and how being a developer was also about being in a constant mode of change (of learning new technologies). It sure sounded a bit scary, never being good enough.

Education: Having studied at university before, I can compare it with my current JavaScript developer education (Higher Vocational Education). The university education in Library and Information Science had no practical moments and zero courses that directly prepared me for the tasks I would be working with as a librarian. Instead, they were broader and gave me better tools on how to learn and think and how to put my future role as a librarian in context. Did I feel ready to start working when I finished my studies? Somewhat? Maybe? Not really? In the end, I was ready, and I did fine.

In contrast to university studies, my current studies are solely practical. I argue this makes the question “Am I good enough?” relevant. After a university degree, you are not supposed to know everything beforehand. However, you are supposed to be able to learn it and use the knowledge to build on top of the foundation you got from university. Given that we only acquire practical knowledge, it is natural to think we must know the technologies 100%. 

Since mastering the entirety of a programming language, or even a framework, is nearly impossible (at least in 2 years). Instead, I tried to summarize what I know and need to improve.

What I’ve learned: I’ve gained foundational knowledge in various technologies, including React, Vue, HTML, CSS, Git, Agile methodologies, Docker, SQL databases, and essential development tools. However, I recognize the need to deepen my understanding in certain areas, such as project structuring, maintainable code practices, advanced framework usage, type safety, caching, and performance optimization.

Unknown Unknowns or my Terra Incognita: The elusive category of unknown unknowns presents a challenge, but my education and internships have provided some insights, reducing the scope of this category. Hopefully, there are no dragons or lions here. I hope to explore it all, avoiding the Dunning–Kruger effect (can it be done?) of overestimating my knowledge.

Conclusion: I’m uncertain if I’m ready for a junior developer role. However, I’m clear about what I know and what I still need to learn. Rather than focusing on whether I’m good enough, I will do my best to embrace continuous learning and strive to find fulfilment in the journey.

Related posts

Why a blog?

Similarity

12%

Obsidian extensions

Similarity

11%

Learning CSS Properties

Similarity

8%