No memory is me being hyperbolic but it’s severely limited. So I feel like reading a manual line by line means I get much less out of it but it’s a large amount of time invested. So I have to factor in that my retention vs time on task is pretty skewed. It’s frustrating. I need to do something a few times to learn. Learning by reading is not great for me. But tech is a very document heavy industry
So: read the man page, find the switches and options you need and hand write that bitch on a notepad, close the man page and execute the command. It’s tedious but it will help your not-great memory work a lot better.
Most people don’t memorize things just by reading them. If you chose to construct some simple exercises/examples for yourself to learn by doing, this is very normal and in fact a good idea!
No memory is me being hyperbolic but it’s severely limited. So I feel like reading a manual line by line means I get much less out of it but it’s a large amount of time invested. So I have to factor in that my retention vs time on task is pretty skewed. It’s frustrating. I need to do something a few times to learn. Learning by reading is not great for me. But tech is a very document heavy industry
So: read the man page, find the switches and options you need and hand write that bitch on a notepad, close the man page and execute the command. It’s tedious but it will help your not-great memory work a lot better.
Or easier, just fire up multiple tty’s. The poor person’s tabs.
What does tty mean in this context?
In this context it is multiple command line instances, like multiple terminals.
https://tldr.sh/
https://cheat.sh/
Most people don’t memorize things just by reading them. If you chose to construct some simple exercises/examples for yourself to learn by doing, this is very normal and in fact a good idea!
Thanks I’ll give that a try.