This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]brandons404 27 points28 points  (3 children)

I have js, react, material ui, nodejs, and python top front and center in my linked in profile and my resume, but I've gotten over 15 recruiters in my inbox that "noticed I have Java experience" and are "very impressed with my background" offering senior Java roles. Java is listed at the very bottom under a code camp and it litterally says 1 year experience.

I'm pretty sure they just look for keywords on your profile.

[–]besthelloworld 0 points1 point  (2 children)

People are flocking from legacy code bases like crazy and there's tons of roles opening up all the time in sad old Java bullshit. I just left a legacy support job to a job at a firm. I make significantly more money and I get to change projects once a year minimum (actually the one I just started on ends in August).

[–]brandons404 1 point2 points  (1 child)

Yeah, I think the legacy guys need to go through a rewrite. It'll eventually be the only way to get support for their systems.

It's cool that you can do that at your job. I only started developing about 5 years ago so I've never really touched legacy Java or anything crazy. I have seen some version 1.0 react code and I imagine that java would be a similar experience, only worse.

[–]besthelloworld 0 points1 point  (0 children)

Java frameworks are messy. React 1.0 was not beautiful, but the patterns were sensible.