I’ve been bat­tling a Python for the bet­ter part of a week now. Mostly just in terms of cre­at­ing a nice habi­tat for it to inhabit, so that we can gather all man­ner of use­ful infor­ma­tion about the habits of pythons and inter­ac­tions of humans with things that the python does. I’d been win­ning most fights and attribut­ing the fact they arose at all to my slowly becom­ing famil­iar with the way it worked at all.

I’d been doing some research on this par­tic­u­lar kind of snake for a cou­ple of months before I decided it looked like a GoodThing™ to be wrestling with, so I knew a bit about it rel­a­tive to some­thing else that I knew a bit about (enough to be dan­ger­ous, as is appar­ently the case with 95% of the world’s PHP devel­op­ers). I knew that it was slightly more strongly typed than PHP, but didn’t really think that was some­thing I’d have to know about.

Ba-baauummm.

Error in formatting:__str__ returned non-string (type int)

Oh, come on, just play with the pretty lit­tle num­ber. Grum­ble grumble.

I am in the strangest place right now. It’s 1.30 in the morn­ing on a week­night and I’m writ­ing code, but I’ve spent most of the day going between Pho­to­shop and a cock­tail of a cou­ple of shell ses­sions mixed with php­MyAd­min and a bit of Django doc­u­men­ta­tion. It’s cool being able to write use­ful code again (and, bet­ter still, I am work­ing on code to solve prob­lems I’d be itch­ing to solve for our own min­istry con­text at TACKLES/Matthias but am being paid to do it under the aus­pices of the CYIADA project, which means I can afford to spend more time and do it prop­erly!), but it’s pos­si­bly even cooler to have ready access to great design tools at home since last week — qual­ity tools are an awe­some blessing!