Monday, January 16, 2012

Handy: Look up Kanji by Drawing your Query

If you are studying Japanese and come across kanji you do not know how to pronounce, you might find this link very handy.

http://kanji.sljfaq.org/

This website allows you to look up kanji by writing it using your cursor.  I have made use of it numerous times while studying the language.  One of my favourite methods is to watch Japanese television shows like NEP LEAGUE, a game show that features hiragana, katakana and kanji writing and recognition.  If I can't recognize a kanji character and I don't know how it sounds, I come to the kanji dictionary site to draw it and look it up.  This often occurs when I see kanji from signs, brands and questions on the game show.  It's a great exercise for stroke order and for learning by association to the character and the images that accompany it on the show.

Wednesday, January 4, 2012

People Power

I've been working at a University for about three years on a part-time basis in the IT department. The thing I've come to value the most about working here is the people and the levity and support they bring.

My boss appended a comic to the end of our next meeting agenda.

Tuesday, January 3, 2012

Not one to keep her feet firmly on the ground.

Timing is a challenge in photography. For photographer and seemingly levitation master Natsumi Hayashi, it takes persistance to overcome it.


It takes her over ten seconds minimum to set up for each photo attempt. She can try a hundred times a day before she gets the photo she wants. She also shoots solo sometimes - Without someone to hit the shutter button for her, she uses the timer on her camera to delay the shot until she can get into position. The results appear to defy the laws of physics. Hit the link for her website with more photos. http://www.yowayowacamera.com

Tuesday, November 23, 2010

Gmail is Brilliant

I was writing an e-mail to my group mates about a project we are working on. Being the proactive and perhaps overeager beaver I am, I mentioned in the e-mail that I would attach a few docs.

I clicked send - only to realize I forgot to attach said documents.

To my surprise, however, Gmail handily displayed a message box: "Did you mean to attach files? You wrote "Attached is" in your message, but there are no files attached. Send anyway?"

How handy is that?! Completely saved me from making an ass of myself. Now go forth and send e-mails without fear of forgetting e-mail attachments - that is, if you have a Gmail account, in which case - Get to it!

Hyperbole and a Half

Gosh. I neither have the time nor the concentration to tell you how funny Allie's blog is. And I know I shouldn't pretend that I know her or link her blog or mention her name like I know her (since I don't). But I think it's worthwhile.

Just... See for yourself.

Thank you for the link, Phil.

Thursday, May 20, 2010

TableAdapter Wizard Query Parsing Quibble

I was working on a little project in Visual Studio 2008 using an SQL database. I went to add a TableAdapter to add some databound features on my form. I was having trouble with my query, but I had written similar queries in other TableAdapters and wanted to leave the wizard to have a peek. Seeking to save myself some typing, I left my query incomplete and I OK'ed my way through the wizard and ignored the parsing errors. I copied some code from another query and re-opened the wizard. The query worked like a charm now. The wizard didn't complain about anything - that is, until I hit the Finish button. I got an error message saying "There was an error parsing the query" followed by the token, line number and offset.

"Hey, what gives? My query is fine!" I was ready to slap a kid, Masahiro Chono-style.

But I figured it out.

For some reason, when you OK through the wiz on an incomplete or bad query, it sticks in the wizard's memory. Now, when you go back to the wiz and type in any query, it will still attempt to parse the original incomplete or bad query stuck in memory.

I was able to reproduce the error by leaving out the column name of the last line of my query, a GROUP BY statement. The token pointed at the BY keyword when I OK'ed through the wiz. This is understandable since you need to give a column name when using the GROUP BY statement. I then reopened the wiz and removed the GROUP BY statement, making it a healthy query. Guess what? The token pointed at the BY keyword still, even though there was no longer a "BY" in my query!

I worked around this by simply copying the query I wanted, deleting the erroneous TableAdapter, creating a new one, and pasting the query in during the wizard.

Lesson learned: Never OK through the TableAdapter wizard with an incomplete query!

Wednesday, May 5, 2010

Building Academics: Student Initiative to Benefit Institute's IT Services

I'm working on a simple, client-based application to help Student Computing Services manage the inventory of over 960 software titles and the accompanying licenses that they deploy across their four campus locations. But getting here was a little tricky.

At first, I proposed a web-based application. I sought the accessibility of the Internet.

Through several iterations of revising and eliciting client feedback, I learned that the political and jurisdictional circumstances of the client's environment prevent the deployment of a web-based software inventory system. One of the project requirements is that the Student Computing Services Section must have full jurisdiction over the product. This will not be possible with a web-based system. Hosting the database through a free hosting third-party is a security violation. Creating a database server will not be possible without crossing into the jurisdiction of the Networking Section.

The project was forced to become a client-side application. Though very limited in accessibility relative to a web-based system, the client assures me that it will be very useful to the Section. The project will still meet the requirements of the directed field study. It will still be a work of adequate significance and an excellent opportunity for the student to learn and gain experience. It will still involve the planning and development of a database and an application to interact with it.

For now, somewhat disappointed but still determined, I'm continuing to revise the concept and toss the idea around the office to get some feedback. I need to take care not to speak too loudly, though. There's a certain way of doing things around here, see.

Coding begins next week. For the full calendar of events, see this weblink.