I agree with everything that has been said above. However, let me provide some context:
Depending on your interest, skill, stage in professional life, resources available (time/money/supervisor's blessings, etc.), you may fall somewhere in the spectrum ranging from a designer who wants to be able to communicate with an FE analyst, to a card carrying FE analyst, all the way to a developer. Designers are the closest to products (i.e., real world) and developers are the furthest (i.e., general abstract world); developers have the strongest hold on what is inside the 'black box' and the designers the least.
Think about these things, where you want to be in a given time-frame with your resource constraints you are operating under, and then consider the suggestions made above.
It is likely that you may not want to be a developer (otherwise, chances are, you would not be asking these questions). So, if you have resources, then register for an excellent FE course or two at a top school so you are 'forced' to write a mini-solver or an element. But that assumes you want to be an FE analyst. If you'd rather just be familiar with the basics, then self-reading from a resource like solidmechanics.org and watching Klaus Jurgen Bathe's videos on YouTube will be more than sufficient.
*********************************************************
Are you new to this forum? If so, please read these FAQs: