never met a part of the stack I didn't like. sr. engineer at clique studios in chicago, perpetual creative hobbyist, bird friend, local gay agenda promoter. she/her. tips: https://ko-fi.com/carlymho
I don't know that I ever specifically thought of myself as a junior/newbie, largely because I went through my early programming days as a hobbyist in junior high and high school. I did start specifically thinking of myself as solidly mid-level/senior when I became able to and comfortable in asserting myself and my opinions and ideas at work, and advocate for the ideas I cared about, I think.
Once I stopped asking myself whether I could actually build something. Nowadays the question is not if it can be built, but instead how long it will take. But, I still don't view myself as an above average dev. :)
Being able to see a project in all of its sides - even the ones you're not skilled on - and to take decisions about them is what it makes the difference to me.
That doesn't mean you won't ask for advices, of course, but rather asking them not with a "How am I supposed to do that?" attitude, but with a "I think I'll do it like this, do you think it can be improved?" state of mind instead.
I sometimes think like this, it just the problem of how long to build it
But actually, time is money, right?
besides there are many problems and skills needed to be considered
how fast is it?
how scalability is it?
how he/she works in team?
etc...
P/S: recently I join a project which was implemented so poorly and had many issues of performance and now losing customers due to that.
I started to feel like I wasn't a newbie when I could start having productive conversations with more senior employees about the requirements and functionality of an application.
Knowing how to write code is one thing, but to have a vested interest in developing a product and contributing to it from design to production meaningfully is what made me really feel like I was a solid contributor.
I realized I was seeing only the the first inception level.
After you master one insignificant sliver of software craftsmanship, you look up to realize there has been a firehose pointed at your face the whole time. Learning to drink becomes more important than the specifics of any one skill in particular. You get used to it.
For new skills, I still feel like a junior starting out. But, that does not last too long anymore.
I am starting to pick up Node. It's not my first language. It will not be my last.
I think I did when it disappeared from my job title once I changed job.
I guess though that the right thing to do is never stop to think about yourself as a junior, in every field there is always something new to learn, and there will always be someone who knows more than you do. As a personal rule I never let my job title blind me.
Working as a remote freelancer almost since I graduated from CS engineering school, it took me a while to get there. I think I started to stop thinking that when I started to have to refuse new clients, got contacted for senior positions opportunities & got invited to join "restricted" freelance network like toptal for instance.
Though I do stuffs, each time I look around and see new techs or languages/frameworks it rings in my head that I still don't know anything...dont know if that's a good feeling.
I'm curious about why you're asking this question. I worry that terms like "junior" or "newbie" set up a hierarchy that doesn't need to exist. It can lead to "vertical" thinking - "I'm new at this, so I'm underneath or less than the people who aren't new at this."
In reality as I experience it, everybody is a newbie at something, and folks who aren't consistently placing themselves in a newbie position are stagnating.
Any project has different aspects that will apply to folks of all experience levels - design, problem-solving, documentation, support, etc. A well-orchestrated project will apply folks to relevant problems according to their experience, without placing a judgement on which experience is better. In most cases, it's better to have a variety of experience levels on a team, so that people can have problems to solve that they aren't yet jaded about, or bored of solving, or can't yet get their minds around. It's not that your "worthiness" increases as you gain experience, it's that you are a natural fit for different sorts of problems.
Why do you think these terms shall not exist? There are people who have more experience on a subject while other people trying to learn it. I think its a natural proccess, but I admit that calling someone a newbie is a bit harsh.
Oldest comments (63)
What? You mean it stops at some point? :)
To be honest I'm still struggling with this fact. I mean everytime there's a new tech to learn.
I love that there's so much I don't know and will never learn and I'm still a perfectly fine dev. 😋
What is exactly a junior developer?
Interesting post about it hackernoon.com/dont-be-a-junior-de...
When code reviews stopped to mean that I receive a bunch of comments about dummy issues, but I started to educate through my comments.
I don't know that I ever specifically thought of myself as a junior/newbie, largely because I went through my early programming days as a hobbyist in junior high and high school. I did start specifically thinking of myself as solidly mid-level/senior when I became able to and comfortable in asserting myself and my opinions and ideas at work, and advocate for the ideas I cared about, I think.
Once I stopped asking myself whether I could actually build something. Nowadays the question is not if it can be built, but instead how long it will take. But, I still don't view myself as an above average dev. :)
I second this thought.
Being able to see a project in all of its sides - even the ones you're not skilled on - and to take decisions about them is what it makes the difference to me.
That doesn't mean you won't ask for advices, of course, but rather asking them not with a "How am I supposed to do that?" attitude, but with a "I think I'll do it like this, do you think it can be improved?" state of mind instead.
I sometimes think like this, it just the problem of how long to build it
But actually, time is money, right?
besides there are many problems and skills needed to be considered
how fast is it?
how scalability is it?
how he/she works in team?
etc...
P/S: recently I join a project which was implemented so poorly and had many issues of performance and now losing customers due to that.
Great thoughts.
I started to feel like I wasn't a newbie when I could start having productive conversations with more senior employees about the requirements and functionality of an application.
Knowing how to write code is one thing, but to have a vested interest in developing a product and contributing to it from design to production meaningfully is what made me really feel like I was a solid contributor.
I realized I was seeing only the the first inception level.
After you master one insignificant sliver of software craftsmanship, you look up to realize there has been a firehose pointed at your face the whole time. Learning to drink becomes more important than the specifics of any one skill in particular. You get used to it.
For new skills, I still feel like a junior starting out. But, that does not last too long anymore.
I am starting to pick up Node. It's not my first language. It will not be my last.
On March 14 when I read this incredible article on Medium: Don't be a Junior Developer
I think I did when it disappeared from my job title once I changed job.
I guess though that the right thing to do is never stop to think about yourself as a junior, in every field there is always something new to learn, and there will always be someone who knows more than you do. As a personal rule I never let my job title blind me.
Working as a remote freelancer almost since I graduated from CS engineering school, it took me a while to get there. I think I started to stop thinking that when I started to have to refuse new clients, got contacted for senior positions opportunities & got invited to join "restricted" freelance network like toptal for instance.
Currently rethinking this self-designation.
Though I do stuffs, each time I look around and see new techs or languages/frameworks it rings in my head that I still don't know anything...dont know if that's a good feeling.
I'm curious about why you're asking this question. I worry that terms like "junior" or "newbie" set up a hierarchy that doesn't need to exist. It can lead to "vertical" thinking - "I'm new at this, so I'm underneath or less than the people who aren't new at this."
In reality as I experience it, everybody is a newbie at something, and folks who aren't consistently placing themselves in a newbie position are stagnating.
Any project has different aspects that will apply to folks of all experience levels - design, problem-solving, documentation, support, etc. A well-orchestrated project will apply folks to relevant problems according to their experience, without placing a judgement on which experience is better. In most cases, it's better to have a variety of experience levels on a team, so that people can have problems to solve that they aren't yet jaded about, or bored of solving, or can't yet get their minds around. It's not that your "worthiness" increases as you gain experience, it's that you are a natural fit for different sorts of problems.
Why do you think these terms shall not exist? There are people who have more experience on a subject while other people trying to learn it. I think its a natural proccess, but I admit that calling someone a newbie is a bit harsh.