Instead, you listen to audio sequences and transcribe them directly to the characters of your language. So instead of learning the language visually, you learn to understand the sounds which is far more natural.
There's a great free site that teaches morse code in this fashion if you ever decide to give it another go: https://lcwo.net/
The hardest thing about learning a new language is learning to think in that language, not 1. think in native language 2. transcode to target language. Not only is this quite slow, it leads to very unnatural language. English and Korean have different idioms and ways of structuring sentences.
Since I've been studying Korean for a while now I have certain thoughts I can innately express in Korean and actually have difficulty directly mapping to English.
---
However, one has to start somewhere. I can't really learn a concept in Korean without it being explained in English.. until I'm advanced enough to understand Korean grammar and word explanations in Korean.* One just has to remember that things don't map neatly although textbooks pretend like they do. Over time and exposure, you get a sense for how and when things are really used.
So the real answer is you need to just use the target language as much as you can. The only way to innately grasp a concept is by seeing it and using it.
* It's a bit like bootstrapping a compiler, isn't it?
I did a short foray into learning Morse Code, and I ran into what I found to be the biggest barrier to learning new languages. The bloody lookup table phenomena.
What happens is your mental representation maps the Morse sequence->your primary language character->whatever the message then actually means.
This is a very high overhead mental process, and one specifically advised against by fluent Morse keyers. What you want is to map the Morse pattern->it's representative concept.
Example:
First mental impl would look like ... -> S --- -> O ... -> S Then you mentally reparse that string to get semantic meaning.
Trying to do this for more complex messages blows. Case and point.
..-. --- .-. ....... ... .- .-.. . .-.-.- ....... -... .- -... -.-- ....... -... --- --- - .. . ... .-.-.- ....... -. . ...- . .-. ....... .-- --- .-. -. .-.-.-
Imagine that coming over a line at about 13 to 25 wpm.
You don't have time to decode and reparse. You need realtime streaming and recognition of word units->meaning. No decode phase, just "oh, that's 'blah'"
Same thing applies with other languages. Language is used to nominatively stand in for forms of life. N'est ce pas? In any other language is still indicative of the same form of life/confluence of characteristics, 'is it not?'
It's seems easier when you're younger because you aren't fighting the lookup table phenomena because you're still learning your primary language.
It's why when learning a new programming language, an escalating series of higher complexity Hello World's you've implemented in other languages can be a godsend in getting up to speed.