Showing posts with label typing. Show all posts
Showing posts with label typing. Show all posts
Wednesday, November 14, 2012
Japanese Keyboards
Yesterday I was at a meeting and got the opportunity to use a laptop with a Japanese keyboard. At first, it looks like a regular US keyboard until you take a closer look and realize extra keys are added at the expense of the space bar. The laptop I was using also had a smaller "SHIFT" key on the right side. I was trying to type in a password to a website and kept hitting the wrong key while I was aiming for the right-shift key. Eventually I had to stop trying to touch type and just look at the keys.
It wasn't until I started learning Japanese that I realized there are three different character sets for the Japanese language and all of them are used together. That means you can have all three in a single sentence. I understand the basic principles of how to use a Japanese keyboard, but am not an expert. It helps that most Japanese words can be "Romanized" or converted to Roman characters (those are the characters in the English alphabet). Then conversion software coverts the Roman syllables to the correct Japanese characters.
I am impressed that the Japanese have figured out how to adapt keyboards to their complex character sets. I'm glad I don't have to try and figure it out though as my fingers have the US keyboard pretty well memorized. I say my fingers have the keyboard memorized because if you ask me, I have to think really hard where specific keys are but my fingers jump right to them. Now if I could only figure out how to teach my fingers to spell.
Labels:
character sets,
Japanese Keyboard,
typing
Tuesday, December 1, 2009
Bad Typing
I have always considered myself a fast typist. I also think I am fairly accurate. This morning I learned that I am delusional. While I may be fast, I am not accurate at all.
One of my latest software projects is to convert a bunch of Unix cron jobs to Microsoft's SQL Server Integration Studio (SSIS). These are basically reports that query a MySQL database every day at the same time and spit the output into spreadsheets. It sounds easy enough but the queries are about half a page each and there six of them.
When I started creating the project, there was no easy way to copy and paste the database queries. Instead I had to retype them. I felt like I was accurate as I was typing but then came the true test where I ran them against the database. All six of them contained various errors. Some were as simple as using one double quote instead of two single quotes. Others were a bit more severe such as three missing lines.
I was less than pleased with my typing skills and gained a whole new appreciation for "cut and paste." When I couldn't find one particularly tricky problem, I figured out a way to make cut and paste work. Now I just wish I had gone through the effort much sooner. It would have saved me a lot of typing and debugging.
One of my latest software projects is to convert a bunch of Unix cron jobs to Microsoft's SQL Server Integration Studio (SSIS). These are basically reports that query a MySQL database every day at the same time and spit the output into spreadsheets. It sounds easy enough but the queries are about half a page each and there six of them.
When I started creating the project, there was no easy way to copy and paste the database queries. Instead I had to retype them. I felt like I was accurate as I was typing but then came the true test where I ran them against the database. All six of them contained various errors. Some were as simple as using one double quote instead of two single quotes. Others were a bit more severe such as three missing lines.
I was less than pleased with my typing skills and gained a whole new appreciation for "cut and paste." When I couldn't find one particularly tricky problem, I figured out a way to make cut and paste work. Now I just wish I had gone through the effort much sooner. It would have saved me a lot of typing and debugging.
Subscribe to:
Comments (Atom)
