Wounded
02 February 2010
You used to speak so easy,
Now you're afaid to talk [to me].
Its like walking with the wounded.
Carrying that weight way too far,
The concrete pulled you down so hard
Out there with the wounded,
We're missing you.
A thought...
20 October 2009
ruby -le'32.times{|y|print" "*(31-y),(0..y).map{|x|~y&x>0?" .":" A"}}'
Try it!
New Blog
14 July 2009
Check out my new code blog: http://xnot.org and the latest blog post about erlang and Makefiles to simply erlang development!
Accomplice, Hollywood
27 June 2009
My baby brother is in town for holiday for the summer and is visiting me in Hollywood this week. Sam and I took Jeremy to Accomplice, the improvised mystery on the streets of Hollywood. Originating in NYC, Accomplice takes show-goers around the Hollywood Blvd. to seemingly unrelated, uninvolved bystanders wrapping them up into the story.
Carefully choosing my words here as to not give anything away, anyone on the Boulevard can be involved and clues are scattered throughout the day. Even the fellow attendees in our group suspected us to be apart of the show, because we solved a few clues.
I must say that the experience was one I won’t soon forget and will most definitely recommend to friends. They do corporate events too! Highly recommend, even for birthday parties!
Ruby's precedence
08 April 2009
And you thought and was equal to &&
Have you ever looked at ruby code and said wow, this is so readable, I can use and instead of &&, how cool! Well, not quite. There are differences and pretty important ones to consider. Here, let’s see:
The most basic use of and:
a = "b" and "c"
puts a # => "b"
a = "b" && "c"
p a # => "c"
Notice the precedence issue? With and, the precedence is on the left-hand side while && runs through the entire phrase.
Why is this important? And and && phrases, in practice are generally used in if statements and this would cause a big issue with and statements. Why? (Example time)
1 == 3 and true # false
1 == 3 && true # false
true and 5 == 5 # true
true && 5 == 2 # false
Did you catch that?
true and 5 == 5 # true
It’s clearly not the logic you’d expect when you are using and… One more just to prove my point
"hello" && e = "world" # world + world
"hello" and e = "world" # hello + world