I would say that it is more about being aware, unless the role you are performing requires that specific knowledge. Otherwise let your job teach you any long term knowledge in your field versus being expected to know all of those items, even if it's not needed in your current role.
As far as what you should know: problem solving and the process of problem solving in the context of designing and writing software.
This comes from practice and having a good foundation of how to approach problems.
I would say that it is more about being aware, unless the role you are performing requires that specific knowledge. Otherwise let your job teach you any long term knowledge in your field versus being expected to know all of those items, even if it's not needed in your current role.
As far as what you should know: problem solving and the process of problem solving in the context of designing and writing software.
This comes from practice and having a good foundation of how to approach problems.
For example: coderhood.com/5-problem-solving-sk...