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.
Seasoned Staff Engineer at Artium, expert in agile methodologies and software development. Adept at leading teams and pioneering transformative solutions.
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.
Oldest comments (62)
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