Over the years I learned to take my time finding a good opportunity instead of rushing into a partly-fitting job just because my skillset is matching the requirements, and as I spend most of my June looking for a new permanent position, I attended the usual bunch of meet-ups along the lines of JavaScript, Golang, JAM-Stack and network security.

Pizza, Mate And Insecurities

I usually went home having mixed feelings about the conversation culture on such events, and that isn’t because I don’t like talking about tech over pizza and mate, but because I felt that it was pretty hard to stay authentic and somehow me while engaging in the conversations.

Even several years into engineering, embedded & electronics (<3), I am aware that there’s a lot of stuff I don’t really know yet. More than this, that array of stuff gets even larger the more I dive into certain fields of tech. The more I learn, the more I become aware of the things I don’t know.

Even with the experiences I have, I wouldn’t call myself an expert in most of the languags and tools I work with, neither in Golang nor C. I would however say that I got a lot expertise in JavaScript/TypeScript and server administration, yet, even in those fields, there are things I haven’t done yet and I still have a lot to learn.

Me, Expert?

When I talked with people at those meet-ups about fields I have worked in, I always felt bad and as I wouldn’t meet anyones expectations, by admitting that I wouldn’t call myself an expert. I am just a curious geek who has fun throwing code on problems to solve them; being hyped about what’s out there to do so in a better way.

Being open about the fact, that you’re not a know-it-all, doesn’t mean that you’re a bad developer; it just means that you’re human, even though I felt like I’ve made myself vulnerable; which should be a good thing to make software development a more welcome, more open and less gated community.

Here Be Dragons, Forever!

If you’re new to this industry and maybe stumbled upon this blog post: I am a developer having nearly eight years of experience, and while I did learn so many things, you could fill entire books with, there are still these moments. Moments where I look up the most basic things, moments where I feel like I started coding yesterday. And that’s okay.

Over the years the tools (reading as programming languages, IDEs, frameworks) I use have changed. My focus changed as well, since I started as a graphics and web designer, and am now a developer. However, what stayed the same is the curiosity I have to learn new things alongside with the fact, that I come across a field I don’t know much about on a weekly base.

Embrace that you don’t have to know everything to call yourself a valid developer; since being one means you’re writing code to solve other peoples (or your own) problems; and if you’re doing so, you have all the rights to call yourself a dev.

Wether you’ve got ten years of experience or started coding yesterday, only the questions you’re asking yourself about what you work on change.

Be courageous and honest about the things you don’t know and stay curious and excited to learn about new things.