Episode three in my curry cooking adventure – this time with vegetables! See parts 1 and 2 for the exciting initial chapters. I've finally used up all the garlic and ginger paste I made for the first one.
I was stumbling along in the gloom of another grey day at the WWA. And at 3:30pm it was starting to get dark. Very poor conditions for wildlife photography! Then I noticed a small blue bird on a branch and bingo, there was one of the kingfishers in a spot I'd never seen it before, and handy for me to rest my camera on the rail of a bridge only about 8m away. Here are the best couple of shots I got (the first was actually entirely handheld).
A light but fairly complex taste that's reasonably bitter and hoppy, with a slightly burnt/roasted edge which I'd only usually expect to fine in dark beers and stouts. The bitterness and 4.3% ABV make it highly quaffable, but maybe it's a shade too bitter not to get wearing after a while.
Having ploughed through much of the documentation, done the tutorial and started writing my own little web app, I have some half-formed thoughts about Google App Engine to throw out to the world.
- As far as I can tell, any sort of data aggregation functionality (counting, averaging etc.) just won't be possible as the Datastore APIs don't allow for it. I've tried to think of ways to fake it but even my most elaborate machinations come up against the buffers. The only way to manage it at all is to do counting and averaging piecemeal, manually keeping the aggregate values you need up to date with each individual entity modification. Unfortunately, that means that you can't introduce new functionality requiring new aggregate values after you've already got a million users, because you've missed the chance to record those aggregates along the way.
- Python's OK, but I don't like using indentation as the sole way to define blocks. But I'm sure I can get used to that.
- I really don't like having to put an empty __init__.py file in any subdirectories of my python code. If I don't do that it seems I can't import foo.bar.Thingy. Breaking up code into multiple files in a sensible directory structure is surely a fairly common thing to do, so I'm amazed that Python makes it strangely difficult. I hope I've simply missed something and it's actually easier than that.
- In fact all those double underscores look horrid and are a pain to type. Surely a single underscore would have been quite adequate?
- The overall experience for learning GAE is very sorted. Smooth and well integrated – all you need to supply is your own decent text editor. I'm trying out TextMate, the darling of Mac OS X code editors, but I'm worried to see that it doesn't seem to have been updated for over a year.
It seems to be the done thing these days to learn how to use Google App Engine (and thus Python) within a couple of hours and then hack out a simple web application to prove how easy it is.
Oh dear. Look what they've put right in the middle of platform 4 at St Albans. Right where everybody walks to get to and from the exit. Right where people will smack into it amid a bustling crowd, or whilst walking along looking at the display boards just out of shot on the right. And all packaged up in dull grey for maximum "don't see it till you've walked into it" effect.
It only seems like days ago that I put it up, but now the fake Xmas tree must come down again. I always dread this bit as it wrecks my hands trying to get all the fronds folded together into a streamlined torpedo of bristly green foliage. This year I fought back with heavy duty gloves!
Here’s my second curry adventure from the Curry Bible my wife bought me for Xmas. My first attempt was Butter Chicken and was thoroughly awesome. This one was just as good I’d say, and it should be given all the ingredients that went into it: 8 different herbs and spices!
I took this sequence of shots of a kingfisher fishing (unsuccessfully this time) at the WWA – the very local nature reserve down the road. It's taken from about 40 yards away with a 400mm lens, and significantly cropped for this montage. Not great, but still rather pleasing!
I've just completed the computer game World of Goo, having been thoroughly absorbed by it for the last week or so. I seldom play computer games, but this one hooked me good and proper. I think it's the engineer in me that always love this sort of game, as it's based on a decent 2D physics model that involves building towers, bridges and lots more out of various pieces, most of them gooey and continually swaying.