Comments for stephenwoods.net

Comment on Learning Python by kellan

kellan — Wed, 12 May 2010 01:54:54 +0000

object Coin {
	val rand = new scala.util.Random()

	def toss() = {
		rand.nextBoolean()
	}
}

var heads = 0
var tails = 0
val range = 0.until(1000000)
for (i <- range) {
	if (Coin.toss()) {
		heads += 1
	} else {
		tails += 1
	}
}

println("Heads: " + heads + " Tails: " + tails)

Comment on New Job by stacy

stacy — Sun, 18 Apr 2010 01:32:22 +0000

Oh, wait. Flickr. Nevermind. All is right with the world.

Comment on New Job by stacy

stacy — Sun, 18 Apr 2010 01:31:47 +0000

Ah, crap. Who’s going to tell me what they’re saying on devel-random?

Comment on Learning Python by Stephen

Stephen — Sun, 21 Feb 2010 08:40:31 +0000

You and I think alike without sleep. ;P

Comment on Learning Python by Luke Smith

Luke Smith — Sun, 21 Feb 2010 07:48:10 +0000

Well, technically, done once after the loop shouldn’t change the results much. For some reason (read: lack of sleep) I thought it was in the loop

Comment on Learning Python by Luke Smith

Luke Smith — Sun, 21 Feb 2010 07:45:32 +0000

Did you try the js/node version without JSON.stringify? It’s a far more complicated operation than just printing output.

Comment on Back to the Future, Explained by Isaac Z. Schlueter

Isaac Z. Schlueter — Mon, 24 Aug 2009 19:04:21 +0000

You can do it with less code:

var dadWriter = false;

var marty = { isDadWriter : (function () { var dad = dadWriter; return function () { return dadWriter; }; })() };

print(marty.isDadWriter()); //false dadWriter = true; print(marty.isDadWriter()); //false

Comment on Prototyping… by Isaac Z. Schlueter

Isaac Z. Schlueter — Mon, 24 Aug 2009 19:01:29 +0000

You’re not being a baby. You’re being rational.

You should write your prototype using whichever framework you’re most comfortable with, which may be no framework at all. Make sure that the relevant bits are separated out as much as possible, so that it won’t be too terrible to move to something more powerful later.

A prototype needs to get done and thrown away as fast as possible. If a framework doesn’t serve that end, then don’t use it.

Comment on Prototyping… by Laurie

Laurie — Mon, 24 Aug 2009 17:56:40 +0000

It depends how complex the prototype is. If it’s proof of concept I just go without any framework. If it’s a little bigger I go with Code Igniter or Zend.

I would never prototype anything in symfony; it’s very heavy and has big start-up costs, to say nothing of the learning curve if you’ve never used it before.

People sing the praises of prototyping in Rails but I’ve never got around to learning it properly, so there would be another big startup cost there.

Comment on Back to the Future, Explained by Zach Leatherman

Zach Leatherman — Fri, 07 Aug 2009 12:58:24 +0000

Yes, this is awesome!

Can you supply a code sample to describe Einstein the dog?