Earlier quoted context omitted.
Typing fast is one of the greatest strengths for programming for me personally, especially when compared with Vim. It's that that it's a limiting factor, but rather I max out typing quite often, and also I have always wanted to hit 200 just for fun, but it currently feels not attainable. Some people say they spend more time than they do typing, but I definitely don't find that to be the case very often.
I am a bit jealous (maybe?) that typing speed is a factor for you. I am the kind of person that will think for minutes at a time before writing a single line of code
Show HN: I automated half of my typing
141–150 of 331 posts
Re: Show HN: I automated half of my typing
#142Also the most surprising part of doing this was seeing that abbreviating super short words like "the" -> "t" actually saves far more characters overall than abbreviating long words and phrases that are less common, like "what do you think" -> "wdytk".
https://github.com/Ikcelaks/keyboard_layouts/blob/main/magic...
Re: Show HN: I automated half of my typing
#143I feel like typing is never really the bottleneck for me except maybe in some chat interactions would have benefited from the extra bandwidth of video or audio. Do you actually save time on task with these kinds of shortcuts?
Re: Show HN: I automated half of my typing
#144This is neat! I've thought about doing something similar with my shell history to help me figure out which shell aliases I should create.
I use shell functions for this type stuff, and I have it spit out the command line it's going to run with all the args (to stderr) and then running the command, and other sorts of programmatic touchup (tell me if i'm in the wrong directory, or whatever)
spitting out the command line it's going to run with all the args (to stderr) is a function too. shell functions can also do nice things like change the directory in my outside shell, set environment variables, etc.
Re: Show HN: I automated half of my typing
#145Earlier quoted context omitted.
Typing fast is one of the greatest strengths for programming for me personally, especially when compared with Vim. It's that that it's a limiting factor, but rather I max out typing quite often, and also I have always wanted to hit 200 just for fun, but it currently feels not attainable. Some people say they spend more time than they do typing, but I definitely don't find that to be the case very often.
I am a bit jealous (maybe?) that typing speed is a factor for you. I am the kind of person that will think for minutes at a time before writing a single line of code
Sitting somewhere in the middle are dynamic languages where there might be certain implementations (say... some random api integration) where it's simply a lot of code I've typed thousands of times before. This still benefits from fast typing, especially when needing to operate surgically with vim, it's one of the moments I love the most (basically getting 20x combos with perfect typing at high speed when moving/modifying/transforming blocks of text etc etc)
What benefits least of the 3 is writing things like Golang where it still definitely helps typing fast, don't get me wrong, but I usually have to think more there. Pace is slower, and symbols can become a pain in the ass.
At the end of the day... you're still typing thousands of lines of code regardless of whether you're thinking or not. I never understood the argument "I spend more time thinking than coding". You are still going to write the same amount of code whether you're thinking or not. My ideal world (why I love typing fast) is that that time of me coding gets brought down by 50-200% over someone who types slow. I use that time for accelerating ahead. Ie... prototyping and deleting tons of code before refining/cementing in a design is painless.
Re: Show HN: I automated half of my typing
#146This is a very clever idea. However, I realize that I would never want to use something like this that would change over time. E.g. if I ran it every 6 months and last year "db" produced "debug", while this year it produces "database". Because talk about messing up my muscle memory and habits. And the language I write changes very much over time. So I'd actually be much more interested in a "universal" version of thi…
> E.g. expanding "t" to "the" seems like a no-brainer, just like "st" to "something". Is there a minimal set of, say, 200-500 of these that could simply be turned into a "standard keyboard" that everyone could learn? Is it a "no-brainer"? I would map "st" to "start".
Re: Show HN: I automated half of my typing
#147I have spent a good deal of time trying to create text expansions for myself. (manually) It is a lot harder than I thought it would be. To find aliases that dont misfire too often and provide enough value. Give that I daily communicate in several languages that adds even more trouble. I have now split it by application. Different aliases for different applications. I still have misfires. Mostly I have found I need de…
I wish OP's tool suggested aliases for longer phrases than what I saw in the readme. I heard TextExpander for MacOs does that but I am not a Mac user.
Re: Show HN: I automated half of my typing
#148Re: Show HN: I automated half of my typing
#149Earlier quoted context omitted.
I am a bit jealous (maybe?) that typing speed is a factor for you. I am the kind of person that will think for minutes at a time before writing a single line of code
It's definitely situation dependent. When writing a lot of frontend code (vue, typescript, css, tailwind, html) I know what I'm typing several mental steps before I actually type it, so speed gains there are most pronounced. Sitting somewhere in the middle are dynamic languages where there might be certain implementations (say... some random api integration) where it's simply a lot of code I've typed thousands of tim…
Re: Show HN: I automated half of my typing
#150Earlier quoted context omitted.
It's definitely situation dependent. When writing a lot of frontend code (vue, typescript, css, tailwind, html) I know what I'm typing several mental steps before I actually type it, so speed gains there are most pronounced. Sitting somewhere in the middle are dynamic languages where there might be certain implementations (say... some random api integration) where it's simply a lot of code I've typed thousands of tim…
for me philosophically code is a liability. Every line of code I write is a liability for me and future generations. So I try as hard as I can to not write code at all so it takes me quite a long time to decide to write code. I see it like that in the places I work too, I get paid to decide when it makes sense to write code eg introduce liability to the business
Edit: Not that "high volume" means anything but I put that there to illustrate there's millions of dollars of liability on the line, not just pet projects or something. It just sounds like a different kind of business I'd guess. Working on a team is definitely something a lot different, that I don't really deal with, nor have much experience with.