Not so short introduction
After you've read enough literature in English you can be certain most of the time how even difficult words must be spelled. Even if you don't know the rules. "Gut feeling" as some might call it.
Now, if someone comes to you and asks how a word must be spelled you might be able to help, but you can't really explain why you prefer such spelling. Because you didn't learn the rules, instead your experience tells you that it just sounds right. You've got the idea.
End of the not so short introduction
Are we software developers or poem writers?
Imagine yourself a software architect with lots of experience in developing applications of different shapes and sizes.
Your position requires you making difficult decisions to choose an appropriate design pattern for the give problem, a database type or a data transfer format. Suppose you are able to make a right choice most of the time simply because you "gut feeling" tells you what to do.
How do you explain your decisions to a new guy in your team?
"Why do you do something the way you do?" asks the guy.
I just want you to understand that without knowing the alphabet it can be challenging to teach someone a new skill.
If you are lost when you see acronyms like MVC, DBA, SOLID, DRY, DSL, CDN or
if you can't tell the difference between a callback and a postback, static and dynamic typing, authentication and authorization and so on how are you going to stay in the market?
I know it doesn't exactly look like a tip, but the importance of knowing your subject is profound and if you didn't pay attention in school it's time to upgrade your vocabulary.