Https://typequicker.com Building a typing application that helps you quickly learn and improve your typing. We believe everyone can type at 80wpm or more. It just takes a good tool to help them and a couple months of consistent practice. - Source: Hacker News / 2 days ago

Learning something new often can take as little 10-15 minutes a day of focused time. If you do it consistently, it becomes easier and easier to maintain, and it starts to require less and less mental capacity to start > You can learn new things. Pixel art, touch typing, 3d modelling, music, calligraphy, wood working, knitting, a language. Whatever is practical and calls to you, you can learn. Shameless plug: if... - Source: Hacker News / 11 days ago

Building the most effective typing application. https://typequicker.com. - Source: Hacker News / about 1 month ago

Building https://typequicker.com An AI first typing application. I think anyone can learn touch typing and potentially 2x their typing speed. We make typing practice engaging and data driven. - Source: Hacker News / 2 months ago

TypeQuicker (https://typequicker.com) - personalized and engaging typing application. Anyone can learn to type fast - I think it just takes the right tools to make it interesting enough for the users to use daily. - Source: Hacker News / 4 months ago

There's a guide on the subreddit wiki on how to format code for display on reddit. When in doubt, you can also use GitHub Gist or Hastebin, though. Source: over 4 years ago

In future, use code formatting or put your code into hastebin.com and then post a link here. It will make it easier to read. Source: over 4 years ago

If you want to post a log, you'll have to generate one first (go to settings > logging and set both logging verbosities to 0-debug and 'log to file' to ON, then do whatever you need to do to create the offending behavior; that should make the log. Then, open the resulting log in a text editor and copy/paste the contents somewhere like hastebin.com and post a link to it here). Source: over 4 years ago

Close RetroArch, then navigate to your 'logs' folder in your RetroArch user directory (if you can't find it, open RetroArch and go to settings > directory and see where your 'logs' directory is located). You should see a text file there. Copy/paste its contents somewhere like hastebin.com and then post a link to it here and I/we can take a look. Source: over 4 years ago

Can you give me the entire command history that got you to where you are now? If you can do that, make sure there is not personal information in the history, especially passwords. Look at the output of history. If it's large, try hastebin.com . Source: over 4 years ago