Honestly, I should probably just apply to some places and see if I can get a better job, but for some reason I am afraid I will just get turned down.
Consider it rejection therapy, then. It turns out it’s OK to be turned down; and you might at least learn something about the interview experience.
Some thoughts:
Try working for a larger organization where there are more diverse internal opportunities.
Try working for a much smaller organization (i.e. a startup or small nonprofit) where you are compelled to work on different aspects of the project.
Try programming-as-sport: programming competitions such as Ludum Dare.
Try a different technical hobby — learn digital electronics, for instance.
Find an open-source project that you already have an incentive to work on. Do you use an open-source text editor or other tools? Are there features you’d like those tools to have?
Ludum Dare is awesome because it’ll get you into a mindset of developing quickly. Probably best to do that after developing properly for a while, though (test driven development and all).
Thanks for responding, this is a good comment and I have considered some of what you suggest.
I do work in a very large organization, and there is a huge amount of technology in use here. The big problem is that technology is a cost center. They will never (without major changes to how the business works) do anything technologically innovative due to this. That is part of my problem with it.
I am looking at several startup jobs in the area that use more interesting technologies. I’m hoping that my incomplete side projects are enough proof that I don’t only know/care about Java.
I use a ton of open source stuff (emacs, rails, countless libs) I just have problems putting myself out there when it comes to contribution.
Rejection therapy is just like ignoring the cause, but leaving the cause itself unattended. So, it does more injury than helps. Man should focus instead of reasoning that “what makes that flinch? what is the reason for it?”, becouse there is still that cause. Just ignoring the flinch (or even rejection programming) is like kicking the big rock again with bare foot.
It can also be that man is on the totally wrong place or applying on a wrong basis, wrong work… etc.
Also my experience is that in this phase—writing CV and cover letter, is more or less “beauty contest” for Jack-of-all-trades which has absolutely nothing to do with personality or skills itself if the listener is not in front of You and you have your programs with You on that moment to show.
So far my best chances to get work as always been 9 of 10 choices a miss and lost energy. Just making a visit was always the quickest way and through mutual friends.
Consider it rejection therapy, then. It turns out it’s OK to be turned down; and you might at least learn something about the interview experience.
Some thoughts:
Try working for a larger organization where there are more diverse internal opportunities.
Try working for a much smaller organization (i.e. a startup or small nonprofit) where you are compelled to work on different aspects of the project.
Try programming-as-sport: programming competitions such as Ludum Dare.
Try a different technical hobby — learn digital electronics, for instance.
Find an open-source project that you already have an incentive to work on. Do you use an open-source text editor or other tools? Are there features you’d like those tools to have?
Ludum Dare is awesome because it’ll get you into a mindset of developing quickly. Probably best to do that after developing properly for a while, though (test driven development and all).
Thanks for responding, this is a good comment and I have considered some of what you suggest.
I do work in a very large organization, and there is a huge amount of technology in use here. The big problem is that technology is a cost center. They will never (without major changes to how the business works) do anything technologically innovative due to this. That is part of my problem with it.
I am looking at several startup jobs in the area that use more interesting technologies. I’m hoping that my incomplete side projects are enough proof that I don’t only know/care about Java.
I use a ton of open source stuff (emacs, rails, countless libs) I just have problems putting myself out there when it comes to contribution.
Complete at least one.
Rejection therapy is just like ignoring the cause, but leaving the cause itself unattended. So, it does more injury than helps. Man should focus instead of reasoning that “what makes that flinch? what is the reason for it?”, becouse there is still that cause. Just ignoring the flinch (or even rejection programming) is like kicking the big rock again with bare foot.
It can also be that man is on the totally wrong place or applying on a wrong basis, wrong work… etc.
Also my experience is that in this phase—writing CV and cover letter, is more or less “beauty contest” for Jack-of-all-trades which has absolutely nothing to do with personality or skills itself if the listener is not in front of You and you have your programs with You on that moment to show. So far my best chances to get work as always been 9 of 10 choices a miss and lost energy. Just making a visit was always the quickest way and through mutual friends.