Eep on the autocomplete. For me that's a must-have to enable clear code. Calling SomeFunctionWithAReallyDescriptiveName would get pretty painful pretty quickly if I had to type it out every time.
No clue if it's true, but this is why I assumed a lot of older computing stuff is often abbreviated to the point of obfuscation.
For things you write a lot, learning how to quickly autocomplete them can pay off.
I don't autocomplete everything, as picking things from a list is if not slower then at least more annoying than just typing that thing, but for common things it's helpful. For instance I type "game.ReplicatedStorage" all the time, so taking a few moments to learn that "game.reso<tab>" is the same has saved time.
What upped my motivation to learned some shortcuts was switching from one keyboard layout to another (qwerty->colemak) and having 20-30 WPM for a week. Typing everything was so painful that I could doubly appreciate it.
Not really. It's how it should be, except maybe autocomplete. If your code is predictable, it means it has low entropy and you are not using the right abstractions.
No clue if it's true, but this is why I assumed a lot of older computing stuff is often abbreviated to the point of obfuscation.