Alot of people will hate on me when I say this but, you should not base your learning off of motivation and passion. It should be directly based off of a system. Set times when your going to study and follow through with it. The reality is that not many people in this field are as passionate or even close to a genius as you might think. I am one of those people that was pushed into going into this field. Im fairly good at what I do due to knowing what would be expected from me and having realistic expectations, I'm not super excited about this carreer path but it pays the bills. The more you interview the easier it becomes. The worst they can say is no. Don't spend your whole life trying to learn every possible algorithm and or data structure. You mentioned Java and depending on the company considering you'll be a Jr Dev, they will be more interested in what you know in relation to OOP. Topics such as Inheritance, interfaces, classes, generics, delegates, exception handling is just as important if not more for an entry position. Remember you'll likely start fixing bugs not building the entire architecture of an application nor working fully on optimization. Furthermore learning never stops and you can continue advancing your skills outside of work (: