I'm not a professional Java developer, but I work at a company that uses Java, so it just came with the territory to understand things about it, even though I'v

I'm not a professional Java developer, but I work at a company that uses Java, so it just came with the territory to understand things about it, even though I've already had at least a basic grasp of it. I feel blessed that most of the code is mostly straightforward Core Java code (as opposed to any framework-level fun). It is treated a bit like a systems programming language. However, I can agree with this article. It's safely boring to me (despite the fact that having an IDE to write your boilerplate is still necessary for the sake of your fingers.) Since not being a pro at it and not planning to be, I'd rather toy with other things. The job market is diverse in its technical needs. :)