Monthly Archives: July 2014

Geeky Linguist Moment

For those that don’t know and haven’t read the About page.  My education was all in linguistics.  More specifically computers and languages and/or computational linguistics.  Specifically I worked with things like translation software, text processing, and machine learning for things like part of speech.  Computational Linguistics is still something that I have a strong passion for although I don’t get to use it or even read about it very often any more.  That being said, today I found a Google Easter egg.  OK Its not really an Easter egg because its not hidden but I had never noticed it before so for me it was.

defineInitialSearchGiven that I am almost always at a computer I don’t really want to go find a dictionary to check the definition of a word but I really hate using words incorrectly. Of course now I will have to make sure that I do extra proofreading because the minute you say something like that is the minute you make a mistake and everyone points it out.  But just to be upfront I am very picky about many things when it comes to proofreading but a blog is not one of them.  So if I make a mistake in this post or any others please do not get angry.  So on to what I found.  Like I said, I don’t want to have to go find a physical dictionary and I have never liked the interface for the online dictionaries that are available.  They are far busier than I want to deal with.  So I have always used Google’s define functionality.  Now it used to be that you would have to enter a query into Google like this “define: WORD” and it would spit out the word, its part of speech, pronunciation, and definitions.  The system has been updated now so that if you don’t include the colon it will still define the word for you.  But today I noticed something new, there was an arrow at the bottom of the definition.  Now I don’t know when this was added but I have learned that in Google there are often things like this that don’t necessarily stand out but have some cool features.  So I clicked it.

defineExtendedInfo

Well what I found was some very cool linguistic stuff.  That simple arrow unveils the etymology of the word, an option to translate it into other languages, and its usage over time.  If you click on the usage over time graph then you can even go to the Google Books Ngram viewer which is an interactive graph with other searching options.  In summary, there is nothing Earth shattering here and for all I know this neophyNgramViewerhas been there for a while.  But I think it’s cool so I thought I would share.


Ruby on Rails with bluehost shared server

I always like learning new things and I have had a project in mind for a while.  Rather than developing it using PHP, which I am very familiar with, I have decided to use it as an excuse to learn Ruby on Rails.  I use bluehost for my web hosting and to be honest I have had an overall good experience with them.  Although I don’t contact their support often they are usually very helpful.  While searching for instructions on how to get Ruby on Rails up and running and a shared server I found these instructions https://my.bluehost.com/cgi/help/rails  My belief was that because it is in bluehost’s help documentation that this would be the best way to get started.  I didn’t read the whole article before starting because it appears that it is a step by step process.  Well I was wrong so I thought I would document here for anyone else that runs into the same issue.  It is a very simple change that needs to happen but as of today it has not.  Basically you just need to go to the last section of the help article first.  So the order should be

Again this isn’t a big issue but since I didn’t read the full article first I missed the .bashrc setup which means that the environment wasn’t setup correctly.  Another important thing that you will want to do is reload the .bashrc after the changes.  You can do this in a couple of ways

  1. Close your SSH connection and log in again
  2. Run the command
    source ~/.bashrc
  3. Run the command
    . ~/.bashrc

This really isn’t that big a deal but the response from their support was frustrating.  First I was told that I was doing it wrong and that I needed to follow the exact same support article that I had already written them about.  So I responded letting them know for a second time that was what I was doing.  Then the second response, which pointed out the need to edit the .bashrc file to update the paths told me that this wasn’t a tutorial but just a “help file” to reference when using other tutorials.  So one person tells me to follow the “tutorial” and the second person says its not a tutorial.

 

In the end, I got it all setup and now it is time to learn something new.  Hopefully I will have some posts in the future about this project.