Jay McGavren's Journal

...2008, Zyps Contributors.

Zyps has a (hopefully) regular contributor! He just submitted an ExplodeAction with unit tests. (I didn’t even have to ask for ‘em.) And the Environment#<< method he came up with is so convenient (it takes any argument, then calls the appropriate accessor) that I could slap my forehead for not having thought of it myself.

Next he's gonna tackle either a new generic View, or a domain-specific language for Environment setup, wherever his interest takes him. This guy knows what he's doing, so I'll just let him at it.

Edit: Ergh, but he uses double-space characters instead of tabs for indentation. I take all that praise back. :)

rSpec cheat sheet...

Here’s a cheat sheet on rSpec with almost completely raw formatting… I’ll HTMLify it if anyone’s interested.

I'm probably not the first to make this joke, but...

i has can cheeseburger.

Someone was doing a demo at the Ruby users’ group on their MacBook, and a transparent notification popped up that their Website was inaccessible. I didn’t know what app was responsible until just now:

Growl (software) - Wikipedia, the free encyclopedia “Growl is a global notifications system for the Mac OS X operating system. Applications can use Growl to display small notifications about events which the user deems important, in a consistent manner.” Growl (software) - Wikipedia, the free encyclopedia

I’m watching Jeffrey Grosenbach’s screencast on rSpec, and he’s got Autotest (which watches a directory for file changes and automatically runs the appropriate tests) hooked into Growl. He writes a test, saves it, and boom - a frowny-face immediately appears at the bottom of the screen with the failing test. No further effort required. He updates the source code, saves it, boom - smiley face showing the test now passes. No further effort required.

Ruby in general keeps the feedback loop very tight like this (I’m thinking here of Rails’ ability to modify an app while it’s running). Ultimately this is going to produce better coders, faster.

Hmmm, now I’m imagining a Zyps setup that kills the old interpreter and runs a new one every time you save an environment setup…

Hrmmm…

Wrote a script to scrape and tally the number of added/changed lines per day from the Zyps repository…