symlink for a command - affected by its location

[k t]

2013/5/17 Sabniveesu Shashank <shashank16392 at gmail.com>:
>
> On Fri, May 17, 2013 at 7:52 PM, Avi Greenbury <lists at avi.co> wrote:
>>
>> Sabniveesu Shashank wrote:
>> > I created a symlink for an executable in /usr/bin which didn't work. But
>> > I
>> > created the same in /usr/local/bin which worked the way I expected. How
>> > are
>> > these two different?
>>
>> Where was the symlink to, how did you create it, and what happened
>> when "it didn't work"? Do you still have the creation commands in your
>> history?
>>
>> --
>> Avi
>>
>> --
>
> Actual location of command- ~/Sources/nodejs/bin/node
> Command -   cd "-->till 'bin "
>                    sudo ln -s node /usr/bin  [executing 'node' didn't work]
>                    sudo ln -s node /usr/local/bin  [executing 'node' worked
> as expected]

What happened when "it didn't work"?
 command not found : node  ???