Pythian Group

As previously reported, last week-end’s activities could be summarized as me going to town on a yak herd with a lawnmower. And although the rest of Saturday and this morning haven’t been as fast and furious as Saturday morning, there’s a few more things to report:
Read the rest of this entry . . .

Yup. Plucking the alpaca’s eyebrows again, I’m afraid…

You see, because of merciless peer pressure, I’ve revived Perl::Achievements. I thought that would keep the wolves at bay, but noooo… Not a hour after the announcement was sent, I got a new feature request. I really should not but… okay, I wanted to do it anyway and if somebody is actually asking for it, why the heck not? Plus, it’ll give me the opportunity to see if my Template::Caribou is up to snuff.

A few hours later, I have a bug report for MooseX::App::Cmd and (after some touch-ups) released the first version of Template::Caribou on CPAN.

And that’s roughly where things get silly…

Read the rest of this entry . . .

So there I was, leisurely perusing my twitter feed… Oh, an entry by brian d foy? Should be interesting. So I clickety clicked, and let my eyes wander and almost immediatly fall on

Yanick already has perl achievements (although it’s not on CPAN, wtf Yanick? :)

Read the rest of this entry . . .

This is going to be a short one, but potentially useful for anybody writing a Dancer template module, or just plain curious about Dancer‘s guts. So here goes:

A few weeks ago, it came to my attention that Dancer’s Dancer::Template::Abstract, the base class for its template modules, added a test to verify that the template it receives as an argument is really a file. Yay. Sanity tests are awesome. Except… what happens when a templating system is not file-based? A lot of exceptions and a very sad web application, that’s what happens.

Read the rest of this entry . . .

In this modern world, time is a rare commodity. It’s a well-known fact. It has to be carefully budgeted and thriftily spent. There is never enough time to do everything one wants to do, so we have to prioritize, pick what is important and cut our loses on the rest.

I so wish my brain had gotten the memo on that.

Read the rest of this entry . . .

I’m rather fond of Template::Declare. Its killer feature, for me, is how all tags are expressed via Perl-space syntax, which allows me to leverage perltidy to turn any great unreadable glob of HTML into nicely indented code (in comparison, my Mason templates always begin with the best of intention, and end up looking like the indentation fairy went berserk). But it also… irked me. In minimal ways. In ridiculous ways. In ways that I should overlook. But…

I would so love to ditch the global template inheritance that is defined via

Template::Declare->init( dispatch_to => ['MyApp::Templates'] );

and go for a per-object mechanism.

And talking of objects, those OO-like features like mixins and delegation are very cool, but they end up implementing a new OO system. These days, Moose is my hammer, and… wouldn’t it be nifty if the templating system was built using all that antlered magic?

Logic says that I should just learn to live with those small warts and resist the urge to write yet another template system. After all, armies of better hackers went that route, and between Template::Declare, Template, Mason and the many other systems out there, the chances that I’ll come with something better are infinitesimal leaning on the delusional. Read the rest of this entry . . .

Remember that game I have in the back-burner, the one I described as being a cross of ‘X-Com’ meets ‘Dwarf Fortress’?

No? Well, no big surprise. After all, is it way at the back of the back-burner stack. Anyway, as a quick recap: it’s a game about colonial marines blasting aliens in sinister caves to harvest their precious bodily fluids. Or something like that. Important part is: I had some tuits lately, and so I worked a little bit on one of the basics of that game.

Specifically, I checked out how I could dig myself some caves.

Read the rest of this entry . . .

Somebody at $work asked me how I use Git to deploy stuff, probably working under the false hypothesis that wisdom is in any way, shape or form affiliated with yours truly. The fool…

Yet, it is true that I had my share of tinkering with Git, and that I might have gleaned from my experience. So I sent him a couple of links leading to more wisdom-certified sources. They are listed at the end of this blog entry; if you have more good articles/blog posts that you’d like to add to the pile, please don’t be shy and mention them in the comments.

But I can’t just stop there, really. So, if you allow me, I’ll dust off the good ol’ soap-box, hop on it, and share my thoughts on the subject. As usual, don’t forget to take an adequatly-sized grain of salt to go with your popcorn.

Read the rest of this entry . . .

At $work me and my colleages want to set up a LAN radio station, so that we can all groove to the same soundtrack.

To make things interesting, we want to be able to dynamically add songs to the playlist. From any machine.

And since I don’t really have time to do something like that, I’m setting myself a deadline of one evening to get it running.

Got it? Good. For it’s time to rip our shirts. And dance the Haka.

Read the rest of this entry . . .

Git::CPAN::Patch could already seed a local repository with the latest distribution of a module, or its whole BackPAN history, or its GitPAN mirror. But with version 0.7.0, it can now go straight for the meat and clone the distribution’s officil git repository, provided that it’s specified in its META.json or META.yml. Please allow me to demonstrate:

Read the rest of this entry . . .