Comments for Viking Hammer

Comment on The Perch Roulette Simulator by Ross Hendricks

Ross Hendricks — Wed, 17 Mar 2010 03:13:41 +0000

The perch strategy is not incorrect, but it is incomplete. The strategy is mathematically sound up until the 4th step, which directs the better to retreat after a second loss. This is actually the worst time to leave, because each consecutive red (or zero) is exponentially increasing the odds of the next number being a black. Try and flip a coin 100 times, the odds of you landing 7 consecutive “heads” or “tails” are so astronomically low that you could sit for hours and likely never see it happen. The same concept applies to roulette. While it is true that the 2 extra 0’s improve the house odds, this effect is almost negligible compared to the 36 total other numbers. The statement would correctly read that you will virtually never see 7 “non-blacks” or 7 “non-reds” consecutively. So, instead of giving up after the 2nd try, continue to place your bets until you win. The only things you need to be mindful of is a) making sure you have a big enough initial starting amount to ensure that you can do this up until at least the 7th and preferably the 8th consecutive same-colored spin, and b) making sure that you do not exceed the maximum bet up to the 7th and preferably 8th consecutive spin. This is the complete fool proof system.

Comment on Using function scope to build a jQuery event handler by sirsean

sirsean — Sat, 06 Mar 2010 17:56:41 +0000

Actually, it's important to note that the second line is wrong.

li.find('input').attr('id', 'answer_' + answer_index).attr('tabindex', tabindex).attr('value', '');

Because we're cloning the first field, we have to set the value attribute to empty; if we don't, all the new fields you add will start with the value of the first field (which, in this case, is not what we want).

Comment on Using function scope to build a jQuery event handler by Paul

Paul — Sat, 06 Mar 2010 15:48:50 +0000

Yeah I was concerned since the .find changes the scope all the remaining methods act on, but then I decided I’d just ignore that potential issue. Your 3 liner is much easier to read too.

Comment on Using function scope to build a jQuery event handler by sirsean

sirsean — Thu, 04 Mar 2010 23:47:54 +0000

Good call. I tried to go in that direction:

var li = $(append_to + ' li:first-child').clone(true); 
li.find('input').attr('id', 'answer_' + answer_index).attr('tabindex', tabindex);
li.appendTo(append_to);

I had to split it up because I'm setting the attributes on the input element, but appending the li element to the list.

Maybe there's a way to fit it onto one line, but once that "find('input')" is in there I can't figure out how.

Comment on Using function scope to build a jQuery event handler by Paul

Paul — Thu, 04 Mar 2010 21:57:45 +0000

Awesome, I shattered the comment system.

Comment on Using function scope to build a jQuery event handler by Paul

Paul — Thu, 04 Mar 2010 21:57:27 +0000

Cool stuff Sean. I like the scoping trick with the anonymous function.

It's a bit inelegant to use:

$('').appendTo(append_to);

What about doing something like

$('#parent_ul:first-child').clone(true).find('input').attr('id',).attr('tabindex',).appendTo(append_to);

That'll even clone event handlers if you end up binding any to the individual li/input elements.

Comment on A Simple Edutainment Game: It’s Math Bejeweled! by Scott Laidlaw

Scott Laidlaw — Tue, 02 Feb 2010 01:45:21 +0000

Yep, we are working on it. It’s a challenge but let me know if you want a copy of Ko’s Journey in a couple of week for perusal. http://kosjourney.com

Scott

Comment on Flex: Make Sure to Call Super in Item Renderer Override Methods by Vishal

Vishal — Thu, 28 Jan 2010 05:56:32 +0000

This is something new that I have learn today. Thank You

Comment on Open Twitter: What would you name the baby of Email and Twitter? by jaimenm

jaimenm — Sun, 10 Jan 2010 12:32:10 +0000

Agree with Michael…Wave

Comment on Open Twitter: What would you name the baby of Email and Twitter? by Michael

Michael — Sun, 10 Jan 2010 03:09:26 +0000

It sounds like Google Wave which is federated and XMPP-based (think of a public wave). It also sounds like atom/rss plus PubSubHubBub.

They're both distributed systems in which consumers are pushed information they signal interest in.

Surely a federated twitter-type service could be based on PubSubHubBub, or Wave.