February 15th, 2010

Sea dragon

Ozu watching madness. I mean, lameness. Flamenco review.

Well, it's actually been a week since we saw an Ozu movie. Kevin's non-arrival on Friday (he cancelled at about 5 PM and it was just too late for us to make it to a 6 PM show) meant we missed the Munekata Sisters; my lack of sleep last night meant I just couldn't stomach an 8:40 show of Equinox Flower (and getting to bed sometime around 11:30 or maybe even midnight). Maybe I'll see them on DVD someday. I've compensated by buying tickets for the final movies of the festival:

Late Autumn
Saturday 20 February 2010 at 13:00

The End of Summer
Monday 22 February 2010 at 18:20

Early Spring
Wednesday 24 February 2010 at 18:00

The Flavour of Green Tea Over Rice
Saturday 27 February 2010 at 16:00

As ever just nobody seems to have a real interest in seeing these movies with us, but, well, you know. Japanese movies and early music, you just can't get everyone to like everything. At any rate, we had fun people to talk to us in the pub tonight, and they want to do other fun things like go to the Showoff Piano Bar and do hikes and see musicals so that seems pretty close to having it all. I mean, at least we can SEE this other stuff here.

Some of the other stuff we're seeing is some flamenco, and last night we broke in the Sadler's Wells Flamenco Festival (2010!) with Nuevo Ballet Español (yes that's a link to my review) which wasn't brilliant but reminded me of how much I enjoy flamenco, thus sending me off to buy tickets for Eva Yerbabuena for Thursday because, you know, those people who said they'd pay me to write reviews for them are dicking me around and NOT making plans for Thursday for a writers meetup like they said they would. So screw them. Flamenco especially rocks because it's a) five minutes from work b) usually done without an intermission thus ensuring I get home before dead o'clock. So Rawk. And I've got two more shows the following week. All signs point to February being done before I even figured out how to pronounce it correctly.

Er, and, uh, I spent today in training, mostly being frustrated that the guy was trying to teach us his special planning "language" that was guaranteed to remove ambiguity through enthusiastic use of <, [, ( and {. I was unimpressed. I did get the answer to my boss's question from last week ("How can we prove the business value of instituting quality assurance of requirements?") though, so I'd consider the day not entirely wasted. (Answer: 1) Through reducing the amount of time developers are spending on recode work due to misunderstanding of requirements. 2) Through reducing the percentage of time test people are spending writing and researching bugs that were caused by misunderstanding of requirements. Both require analyzing which kind of bugs are caused by misunderstanding of requirements, but it should only take one days' analysis of a project to produce the numbers - maybe two.)