At some point I’ll provide post-to-post redirects, but for now, new content is at sodabrew.com. Cheers!
Originally published at HydricAcid. You can comment here or there.
America, Fuck Yeah!
For a great tearsheet that covers EVERYTHING on the San Francisco ballot, check this out: CaliforniaElection.US.
PLEASE, PLEASE BE PREPARED BEFORE YOU GET TO THE VOTING BOOTH. IT IS A VERY LONG BALLOT THIS YEAR!
This vacuum rocks. It's small and light, with good power, and doesn't have that dipshit design of just about every other vacuum where the vacuum-path runs through the entire hose before connecting to the floor scrubber thinger. Oh, and that floor-scrubber thinger? On this vacuum you can switch it off for hardwood floors!
And it comes in puke green! Kickass!
Also, I need to couch-surf from September 1 - 5 because the previous tenant is still moving out. And I might be dusty. Also we will have a housewarming party! I'm thinking late-September.
When I was in the Czech Republic in March 2007, I went to see a movie called Vratné lahve, which in Czech means “Bottle Return” — although they titled the movie “Empties” in English. There’s a unique feature of Czech supermarkets, a bottle return department, where you return glass bottles of juice, water, and especially beer, and they are returned to the bottling company to be washed a reused without going through an American-style crushing and remanufacturing process. The movie centers around a fellow who loses his job as a teacher of literature and finds work as the man in the bottle return booth at a local supermarket. In the opening sequence of the film, the man is reading a poem to his class, Za trochu lásky… by Jaroslav Vrchlický.
Za trochu lásky šel bych svĕta kraj,
šel s hlavou odkrytou a šel bych bosý,
šel v ledu – ale v duši vĕčný máj,
šel vichřicí – však slyšel zpívat kosy,
šel pouští – a mĕl v srdci perly rosy.
Za trochu lásky šel bych svĕta kraj,
jak ten, kdo zpívá u dveří a prosí.
I’ve been looking for an English translation of this poem since I saw the movie, and thanks to the help of the linguaphiles community of LJ, and my Czech friend Dana, I now have one!
For a bit of love, I would go to the end of the world,
I would go bareheaded and I would go barefoot,
I would go through the ice - but with eternal May in my soul,
I would go through the storm - but would hear blackbirds singing,
I would go into the wilderness – and would have of pearls or dew in the heart
For a bit of love, I would go to the end of the world,
as one who sings begging at the door.
Na zdraví!
Originally published at HydricAcid. You can comment here or there.
Poker in the rear
I made another breakfast, folded the clothes, and put together directions on public transit to get to Sausalito. Easy enough, BART to SF Civic Center, and Golden Gate Transit bus number 10 from 7th & Market.
Ok, but there's a problem, see, with this bus at 7th & Market thing. About two hundred thousand flamboyantly gay people were trying to parade onto the bus, too! Oh pride, how you do fill my pockets with randomly colored condoms.
So now I'm at the Stern Grove, arriving just about halfway into the Rachmananoff piano concerto that Orli Shacham is playing with the San Francisco Symphony. Magnificent piece magnificently played! And shortly into intermission, followed by Tchaikovsky's 4th Symphony :-)
Update: quite apropos for being Pride weekend, Tchaikovsky was gay!. And the symphony was played only just ok, unfortunately.
An effective plugin strategy actually embraces these people and their pet features, providing a mechanism for decoupling code from the code project, yet allowing key features to be injected into the running system from a separate and contained plugins area. Note the words separate and contained. Both are very important.
The plugins area must be separate because you want to protect the clear messaging of your application's features. You also want to keep plugins separate because there can be a tendency to make everything a plugin. Don't. Just don't. Really. Core features are core. They are not plugins. Nobody wants a framework that does nothing until you've loaded a jillion plugins into it in order to create a working application. Sure, you should use code modularization as a programming technique, but don't go overboard. So separate is a double-edged sword: keep the non-essential stuff away from the core applications, and keep all the essential stuff inside the core application. Sometimes it means swallowing a plugin into the app. If it makes sense, do it.
The plugins must be contained. And, ideally, also self-contained. That is, you have a directory like '/your/app/plugins/some_crappy_plugin' for each plugin. The plugins are contained within '/your/app/plugins' and each one is further self-contained another directory level below that. Then, provide an API that allows the plugins to act at a distance. Yes, act at a distance. Normally this is something that you don't want because it is hard to figure out. But in the case of plugins, it is just right. The plugin does not need to patch into the main app code, but rather register itself with the main app and declare which of its functions should be called from which parts of the main app. It's runtime integration, runtime configurability, and runtime enable/disable. Sure it can be slower. But it's so much better than having people distributing patches that implement their functionality by hacking up your beautiful code.
Originally published at HydricAcid. You can comment here or there.
The next 3 days involve: a boat, to catch a bus, to get a train, to go to Bangkok, to pick up my spiffy new suit, and haggle for a tuk-tuk to catch a plane to fly to New York and then to San Francisco!
