Thank you so much for writing such a thorough and insightful response. That was the wake-up call that I needed. I had not considered that putting in so many applications would actually hurt my chances.
This is incredible advice, and while it stings a little to think I may have damaged my chances or even my reputation, it also comes with a little bit of relief. Not only is it okay that I slow down and take my time with applications, but it is seems critical!
I have a lot to think about: how and when I apply to roles, researching roles more and tailoring my resumes more specifically to that role. I am so grateful to you and everyone who took time to give me feedback. That is exactly WHY I posed this question and this community is awesome.
The one thing to remember about the IT world (and it probably translates wider still) - everyone makes mistakes.
We estimate tasks, the estimates are wrong. The tasks themselves are at best, inaccurate. The requirements that drove us to create those tasks are wrong. Customers complain about our software being wrong, and sometimes the customers are wrong.
In your position now, if a recruiter phoned/emailed with something along the lines of "I've got a guy to talk to you about, he probably has a bit of a bad reputation - but that's simply because no-one told him how to get things right at the start, I think he's worth looking at, can I send the resume across?" ... my reply would be "sure, lets have a look."
Getting things wrong isn't a problem, especially when you don't know any better. Putting things right when you know they're wrong is the true sign of character.
While I will agree that I didn't "know any better", I could definitely sense that something was wrong. More specifically, I knew I was doing something wrong. But I didn't know what that was! Which is why I posed this question and I am glad I did.
I always think about the definition of insanity (apparently not a direct Einstein quote!), "Insanity is doing the same thing over and over again and expecting different results."
I am just glad to break out of that cycle and explore new methods and practices, and hopefully learn from my mistakes and right my wrongs!
The bonus to this approach is you are more likely to end up in a position (and at a company) that you ACTUALLY want to be in. There's nothing more soul sucking (even as a jr because let's face it, we deal(t) with some shit as jr's) than working on projects that you have no interest in for a company that you don't value.
One of my teachers in school always preached about how important, in his opinion, that you carefully consider your first position and that you are able to both willing and able to stay there for 1-2 years at least. According to him, you don't want to be bouncing around from role to role, gaining little experience, traction, and possibly even a bad reputation.
So I guess in a way it's a blessing that I haven't been in serious consideration for some roles, because truth is, there have only been a handful of roles that I've really wanted and been excited to apply for.
I think it will really help me to spend some time just researching and narrowing down roles that I truly want to apply for.
That's some sage advice from your teacher. It's far better to take your time and find a jr role with a solid mentor (or at least prospect of one).
It also goes the other way, if you happen to find yourself in a toxic environment, get out! Some jr devs make the mistake of thinking "I just need my 2 years", but it will be detrimental to your mental health and possibly career where it's possible to burn out or become jaded.
I wish you all the best and know if you focus on what you want, it will come your way 👍
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Dave,
Thank you so much for writing such a thorough and insightful response. That was the wake-up call that I needed. I had not considered that putting in so many applications would actually hurt my chances.
This is incredible advice, and while it stings a little to think I may have damaged my chances or even my reputation, it also comes with a little bit of relief. Not only is it okay that I slow down and take my time with applications, but it is seems critical!
I have a lot to think about: how and when I apply to roles, researching roles more and tailoring my resumes more specifically to that role. I am so grateful to you and everyone who took time to give me feedback. That is exactly WHY I posed this question and this community is awesome.
The one thing to remember about the IT world (and it probably translates wider still) - everyone makes mistakes.
We estimate tasks, the estimates are wrong. The tasks themselves are at best, inaccurate. The requirements that drove us to create those tasks are wrong. Customers complain about our software being wrong, and sometimes the customers are wrong.
In your position now, if a recruiter phoned/emailed with something along the lines of "I've got a guy to talk to you about, he probably has a bit of a bad reputation - but that's simply because no-one told him how to get things right at the start, I think he's worth looking at, can I send the resume across?" ... my reply would be "sure, lets have a look."
Getting things wrong isn't a problem, especially when you don't know any better. Putting things right when you know they're wrong is the true sign of character.
While I will agree that I didn't "know any better", I could definitely sense that something was wrong. More specifically, I knew I was doing something wrong. But I didn't know what that was! Which is why I posed this question and I am glad I did.
I always think about the definition of insanity (apparently not a direct Einstein quote!), "Insanity is doing the same thing over and over again and expecting different results."
I am just glad to break out of that cycle and explore new methods and practices, and hopefully learn from my mistakes and right my wrongs!
The bonus to this approach is you are more likely to end up in a position (and at a company) that you ACTUALLY want to be in. There's nothing more soul sucking (even as a jr because let's face it, we deal(t) with some shit as jr's) than working on projects that you have no interest in for a company that you don't value.
One of my teachers in school always preached about how important, in his opinion, that you carefully consider your first position and that you are able to both willing and able to stay there for 1-2 years at least. According to him, you don't want to be bouncing around from role to role, gaining little experience, traction, and possibly even a bad reputation.
So I guess in a way it's a blessing that I haven't been in serious consideration for some roles, because truth is, there have only been a handful of roles that I've really wanted and been excited to apply for.
I think it will really help me to spend some time just researching and narrowing down roles that I truly want to apply for.
That's some sage advice from your teacher. It's far better to take your time and find a jr role with a solid mentor (or at least prospect of one).
It also goes the other way, if you happen to find yourself in a toxic environment, get out! Some jr devs make the mistake of thinking "I just need my 2 years", but it will be detrimental to your mental health and possibly career where it's possible to burn out or become jaded.
I wish you all the best and know if you focus on what you want, it will come your way 👍