I think Gorn's challenge to go job hunting "with a scrubbed resume that doesn't reflect [your] current or recent billable work" is a bit unrealistic. We all have a history and if we are going to go talking to hiring managers there needs to be a common understanding. My 2 cents of course.
You misunderstood what I was asking Pxsant. I asked him to consider using a scrubbed resume when
he tests his method of crash-learning plus hammering interviews to find something available. It's to establish a baseline to see if what he's stating actually works to help someone land a job when they don't have the specific OTJ experience.
It's the equivalent for his method of fasting overnight in order to take a blood glucose test in order to get a proper blood reading.
Not something you'd do in a real life economic survival situation.If you are going to interview for a job, you'll have to know all about the design patterns as well as everything in the 1,400+ page Eckel book.
Also, Android mobile uses Java, but mobile app development does not sound like a skill target.
The bad thing about Java is that because it's so widely used there is going to be stiff competition. And who knows how many Oracle certified Java SE 8 Programmers are out there?
I don't agree with the first sentence. I say it really just depends. Some shops want to see sample code. Others may tech you out on standardized knowledge as you state. It really depends on the sophistication of the place and how much their own staffs who interview you know. I had that a lot when I contracted in C++ - some places are formal, others just want to hear you talk about your interesting project.
I agree with your last sentence. Pxsant seems to be targeting the market leader for programming languages, so Java >> Python. Yet Java is the most generic language on the planet at this point, similar to knowing "just C" in the 1990s. I'd personally go for a language where I could establish some personal uniqueness in my approach.
In my guts I don't think that "cold learning" Java will allow you to land a position, but let Pxsant prove me wrong.
I believe your technical specialization is a bit of targeted marketing. The more generic you are, the more you SEEM to be able to fit more roles, yet the more of a face in the crowd you are.
That's true of cars - dating and selecting a mate - picking reading material - picking a movie to watch on Netflix. You would never pick generic when you needed or wanted specific.
Same with employers.
When I did SW contracting my best successes were in fairly tightly defined language+platform+project type domains. I wasn't everything to everyone. I was something very specific to the rare but extant places that needed that combination of interests.
Example of a successful schtick/niche that lasted me for about 10 years from 93 to about 2005: C++ language; Windows OS with Borland and then Visual Studio tools as platform; Windows application rewrites as the project type.
I believe that Pxsant should figure out a similar triad of qualities for best success, not just figure that learning Java expertly will open doors.
In fact, DAMN, I feel like I just created a new law of programming job physics in this post. Hurray me!
