Posts Tagged ‘suck’

Rumblings from the Secret Labs Rumblings from the Secret Labs

Lost in Translation?

March 5th, 2010
The mere existence of the message implies a history, as well.

Even if you’re not a programmer, take a look at the following lines of code:

public function sendCommunication($oCommunication)
{
    if (self::emailMode != EMAIL_TEST_MODE_NONE) {
        if (self::emailMode == EMAIL_TEST_MODE_LOGGED_IN_ONLY) {
            // DO NOT COMMENT OUT THE FOLLOWING LINES
            // EVER
            // FOR ANY REASON
            // INSTEAD CHECK THE TEST MODE AND SET THE ADDRESS FIELDS ACCORDINGLY
            $oCommunication->to = $oCommunication->from;
            $oCommunication->cc = '';
        }

Now, I ask you, even if you’re not a programmer, you know there’s one thing you would never, ever, do to the above code. Right? Now let’s say you are a programmer, a professional, being paid because of your ability to find solutions to problems and express them in an abstract language.

Now further imagine that changing the above code can lead to the customers of the people paying for this work getting spammed with confusing emails with our client’s name on them.

Yeah, you guessed it.

Rumblings from the Secret Labs Rumblings from the Secret Labs

Jer’s Software Hut Falls Silent

February 28th, 2010
Shutting the doors (at least for now).

The shadowy, misshapen minions have all gone home; the vast underground chamber that once rang with their chants as they turned the giant wooden capstans has fallen silent. The river of lava flows unimpeded, the precarious rope bridges spanning it falling into disrepair. Above, the streets of Sky City Research Facility, once teeming with antigravity cars, are empty, the crystalline architecture acquiring a layer of eagle guano and dust that is transformed into gritty runoff when it rains.

The crudely-crafted Web site at jerssoftwarehut.com no longer accepts payment for Jer’s Novel Writer software licenses, and bears the following statement:

Well, it’s happened; I have a regular job. As I slave away working for the man I often wonder if things might have been different had I only worked harder at making Jer’s Software Hut a business rather than a hobby. Probably now we will never know. It was a good run but it’s time to ackowledge that development is stalled and customer service around here has been really awful.

That pretty much says it all; despite thousands of happy users, some of whom even paid for the software, when it came time to have a steady income again I took the safer path of working for someone else. (The ironic twist to this narrative I will leave for another time.)

It was a good run, and as I get my work life under control I hope soon to at least return to using Jer’s Novel Writer for its intended purpose – as a writing tool that helps me create fiction. Until I do that I can’t even consider opening the shutters on the Hut and throwing the big switch that raises the lightning rod into the violent midnight thunderstorm, while sparks fly and the turbines spin faster and faster, the needles on their gauges creeping ominously into the red. Maybe someday, though. Maybe someday.

Rumblings from the Secret Labs Rumblings from the Secret Labs

A Job I’m Glad I Don’t Have

January 24th, 2010
Even cushy jobs can suck.

As you might be able to tell from the paucity of episodes here at MR&HBI, I’ve rejoined the ranks of the employed. My writing has taken a real beating, so today I’m going to spend some time writing about work. You don’t have to thank me, it’s what I do.

I don’t mind writing software; I’m pretty good at it and I can make pretty decent money doing it. I would much rather write code than dig ditches, for instance, and luckily for me the world has decided that making Web sites is worth more than roadside drainage. (Before you go and say, “that’s because it takes skill and training to make a Web site, but anyone could dig a ditch’, ask yourself – could you dig ditches for a living? If the economy were turned upside-down, that ditch-digger living in his nice house would say, ‘anyone can make a living sitting on their ass in front of a computer, but I dig ditches. I’m glad things are the way they are, is all I’m saying.)

My current job sends me dangerously into territory I don’t much like, however, and that’s the area known as Information Technology. It’s not really a good name for the job, which is about setting up computers and keeping them running. It’s less about making things and more about making things work.

Last night, for instance, I moved the Web product I’m working on to a different server and it didn’t work. Naturally I assumed the problem was in my code (it had worked on that server in the past), so it was several hours later that I discovered that for reasons I still don’t know, the server failed when it tried to compress very large messages. Just *poof* no response beyond the number 500 (something went wrong). To make things more fun the server was specifically set up to not write out a lot of error messages to its log. I turned off the compression feature (with a hammer) and things worked again. Five hours or so spent to add seven characters to a PHP file, to make things work the same way they already did on other servers. Welcome to the world of IT.

I think the original intention of the phrase information technology referred to the the information that would be stored, manipulated, and distributed by machines. What the I really stands for is the vast store of arcane crap you have to know to do that job well. What line of the php.ini file to modify if you want zlib output buffering and utf-8 character encoding. How to set up all the computers in an office to use a local domain name server first. That’s the information in IT.

The worst thing about having an IT job is this, however: When you’re doing a good job, no one notices. When a company is running smoothly, that’s a sign that the IT department can be downsized. There are no problems! What are those guys doing all day? Having things not happen as part of your job description makes for tricky times when you do your job well. Of course, when something does go wrong people know just where to find you.

So if you work in a company that has people on payroll working to keep your technology humming along, cut them a little slack. Someone’s got to do that stuff; be glad it’s not you. I do enough IT now to know that I’d rather let someone else have the pleasure.

Idle Chit-Chat Idle Chit-Chat

An open letter to the retard driving a white compact car on Highway 17 in dense fog with no lights

December 21st, 2009

You, sir, are a fucking retard.

Sincerely,
Jerry

Idle Chit-Chat Idle Chit-Chat

The Book Review that Wasn’t

October 6th, 2009
Lots of words, lost to the ones and zeroes of the InterWebs.

Last night I wrote a review of a book. I was pretty pleased with the results. It actually talked about the book for a while. This morning I tweaked it a bit and hit post.

It vanished.

Well, mostly vanished. The title was there, as was the little blurb at the top. Everything else was gone. “Poop!” I said (or something like that).

I use ecto to compose my larger blog episodes; the offline editor is much nicer than any in-browser editor I’ve encountered, especially on my 8-year-old laptop. I don’t call it Ol’ Pokey for nothing. Plus there are times I want to write an episode but the Internet is nowhere in sight. ecto has been working very well for me. Except when it loses my work. This is the second time, but somehow this one hurt more. Also, ecto was recently bought from the original developer and seems to be stagnating.

“Looks like it’s time to give MarsEdit a serious look,” I said, and downloaded the latest. I fired it up and was greeted with “Your trial period has expired.” Dang. I’d launched it once when comparing ecto and MarsEdit back in the day. MarsEdit was missing a particular feature (don’t remember exactly what) and that made ecto the winner. Before it started losing my work.

Lots of people like MarsEdit (lots of people like ecto, too), but am I willing to pay for it without writing a single episode with it? That’s hard to justify. I’m downloading a program called Qumana to rewrite the book review with. We’ll see how that goes.

Edited to add: Nope. Qumana didn’t work. At all. I checked the system requirements, and it should work. But it doesn’t.

Idle Chit-Chat Idle Chit-Chat

The Worst Thing That Ever Happened to the Internet

September 12th, 2009

Twenty years later, we're only ten years behind. Maybe if I get this off my chest I can spend my sleepless nights thinking about things that actually matter.

I mentioned in the last episode that Internet Explorer was the second-worst thing that ever happened to the Internet. Today I’ll talk about the absolute worst. It’s really a long technical rant that doesn’t matter, but it feels good to let it out. What follows is an underinformed ramble about the scourge that did the most harm to the developing computer network that went on to transform our lives — damage that we still live with today. Without this one corrupting influence, we would have had Internet applications that didn’t suck a decade ago, if not longer. In fact, it was because of this electronic plague that Microsoft was able to cause so much harm with Internet Explorer.

The culprit? The ball and chain that modern technology has dragged along despite its obvious flaws? Hypertext Markup Language, or HTML.

First, let’s start with the name. HTML is not a language. Not even close. It is a document format. That its inventors did not recognize the difference tells you that the wrong guys were doing it.

Second, it’s not a very good document format. At its heart, the inventors wanted a format that did three things: connect related documents, embed external resources (like images) and contain standard formatting information that would be interpreted by viewing software consistently. They were not the only ones developing systems like this; Josten’s Learning invented a similar system when they built the first multimedia encyclopedia for Compton’s New Media. Where Berners-Lee and friends had URL’s, Josten’s engineers created BRU’s, but beyond the initials the function was the same.

I don’t want to be too harsh on Berners-Lee, Cailliau, and the others who grew HTML, but I wish they’d been a little more far-sighted. I say ‘grew’ rather than ‘invented’ because it’s clear that they never sat back and asked themselves “What is a tag? What roles do they perform?” Even now, XHTML, the supposedly more rigorous (if still misnamed) descendant of HTML has fundamental inconsistencies.

For a simple example, take the <br /> tag. It exists because in HTML all whitespace (tabs, spaces, and returns) are mushed together and presented on the screen as a single space. Thus

<p>this markup</p>

and

<p>this
 
        markup</p>

come out the same on the screen. That’s fine if you know what’s going on. But what if you want to put in a line break or a space? Well, for a space you add a special character code &nbsp; and for break you add a tag <br />. Why is one a character and one a tag? Because on the day HTML’s inventors decided they needed line breaks, a tag seemed like a good way to go, even though semantically it had nothing to do with the roles of other tags. It could just as easily been &br; or something like that. That’s how HTML grew up. And thus the World Wide Web was born.

Another fundamental flaw is that the content (what to display) is all mixed up with the presentation (how to display it). What if you want to show the same document in different formats? Nope. While some tags were geared toward identifying the type of content that they enclosed (like the <p> tag), others were direct formatting instructions (like the <i> tag). This inconsistency in the role of tags in a document is a reflection of the organic (and sloppy) way that HTML was grown.

I really can’t blame the inventors of HTML for what came next. Everyone started using it. Everyone. The flaws and inadequacies of the format quickly became apparent. Different document viewers (browsers) rendered things differently. Formatting options were extremely limited. The systems were vulnerable to abuse by unscrupulous people. Right then, there was a chance for people to say, “hold on a second! Let’s take the idea of HTML and apply the lessons we’ve already learned in other branches of computing, and make something that doesn’t suck.”

Rather than scrap HTML, browser makers and others set out to fix it. That was the Big Mistake. After twenty years of tweaking and bickering and incompatible extensions introduced by browser manufacturers and squabbles and lawsuits, HTML has been upgraded from awful to poor. Along the way, companies like Adobe and Macromedia thought to get their technology adopted as a replacement to HTML (the Web in pdf? Interesting…) but those efforts were doomed from the start because they did not provide free, simple tools to create the content.

HTML’s greatest shining virtue (and it’s an awesome one) is that it’s accessible to anyone who can type. Anyone. No special tools required.

So, now we have style sheets to help separate content and presentation, XHTML to fix some of the semantic craziness of HTML, and browsers are finally starting to agree on what all the formatting instructions actually mean. We could have had that fifteen years ago if people had just let go of HTML, but here we are now, with an almost-functional system. There are still plenty of flaws, however. Things that seem so normal now that we don’t even think about how dumb they are.

Take this blog, for instance. It’s a pretty well-built Web application, based on reasonably up-to-date practices. Yet were you to click the comment link at the bottom of this episode, you would go to a new page. On that new page the browser would reload the same header and the same sidebar it just erased. What a waste! Why does it do it? Because that’s how HTML (and HTTP, the underlying part that communicates with servers) works. There have been abortive attempts to fix that over the years, but they have all been flawed. Now, at long last, techniques have been developed to overcome that problem, but they are not quite ready for prime time yet. For one thing, they are very complicated, and for another they rely on browsers working just right. Why was it so hard to implement? Because at its core the Web was not made that way.

Even in the days when almost everyone was on dialup (except the people inventing HTML), no one stopped to say, “hey, let’s make a way to only update the content that changes.” That problem has now been ’solved’ by adding a new layer of complexity on Web sites. By adding this layer (on top of CSS and so forth), we get sensible Web applications at last, but we take away the one super-cool thing about HTML. It is no longer a simple format that can be harnessed by anyone with a text editor. We have lost the attribute that was the only reason to keep HTML around in the first place.

So now we have a system that is both inaccessibly arcane and flawed. Yay!

Reading Reading

Step on a Crack

July 27th, 2009

The sort of thing you read when TV is the only alternative.

On a cruise ship books can make the rounds, passing from one reader to another fairly quickly. Two others in my group read Step on a Crack by James Patterson and Michael Ledwidge before I did. They both agreed that the book was not very good (to paraphrase their summaries as gently as possible), so it’s fair to say that my expectations were low when I picked up the book.

My expectations were met. Had I something else to read, I would have put this thing down around chapter four and never looked back. (The chapters are very short). The first sentence is a confused and awkward bit of imagery (the back of a jacket turns away…) and that sets the tone for the whole book. We start with a murder, the untimely demise of one of the finest people the world has ever known. Her highly-trained bodyguards, who have been protecting her for several years now, are apparently unable to respond to what should be a routine medical emergency. It seems no one told them that their charge was deathly allergic to peanuts so they weren’t able to do anything about it. Oops! (The bad guy knew about her allergy, however, well enough to execute a months-long plot to infiltrate a fancy restaurant in order to put peanut oil on her dinner. Wow.) On top of that, somehow on this particular night the woman forgot to pack her own medicine. And so begins the work of the greatest criminal mastermind of the century.

But wait! Before we go any further with tales of murder and mayhem, it’s time to meet a whole bunch of Perfect People. These people do nothing to influence the plot of the story; they’re too busy being perfect. Perfect children. A perfect stranger to take perfect care of the perfect children in the time of crisis. Perfect people everywhere, doing the perfect things with perfect consistency. Bleeargh. Did I mention they have nothing to do with the plot? They are there, in fact, to perfectly NOT encumber the detective we will be following as the threadbare story develops.

Begin the crime of the century. A crime so big and so audacious it must be the work of a criminal genius. How do we know? Because the authors tell us so. With exclamation points! And occasional nonsensical italics! The NYPD is starting to look like a bunch of incompetent fools, and the press is going to have a field day. If hostages are killed, the press will rake our hero over the coals.

Only, hostages die, and for a long time it looks like the bad guys are winning, but the authors can’t be bothered to portray the actual coal-raking. In fact, the stakes for the good guys never escalate. There is no heat. (One reporter does criticize our hero in her paper, but then immediately expresses remorse and stops her persecution — taking her own step toward perfection before she can cause too much trouble for the authors.)

Then there’s the time the detective walks in and finds his grandfather dressed as a priest! (That’s their exclamation point, not mine.) Wow! what a shock! Only, it turns out that Grandpa has been a priest for years, everyone knows it, and seeing him dressed that way was no shock to anyone. The authors were just yanking our chain a bit. Whee.

Meanwhile, most of the hostages experience life-changing revelations. The perfect hostages become perfecter(!). The imperfect ones get better! For instance, the ‘fashionista’ resolves to go to rehab and stop being such a bitch all the time. Once she makes that decision, that’s it for her in this story. She makes a promise to herself to undergo a complete personality realignment and we believe her and move on. Well, the authors seem to believe her. I’m skeptical.

I hate to spoil it for you, but the good guys win in the end. In fact, they don’t have to work very hard to defeat the brilliant criminal mastermind. Sure, the bad guys got away at first, but just a little routine investigating and bam, there you have it. To avoid the authors having to get too clever, the criminals conveniently explain all the loose ends for us.

I finished the book. It didn’t take long; the type is big and there’s about fifty pages worth of blank space between chapters. One-third of what is left is a sentimental parade of sap that does nothing for the story. I set the book aside and decided not to review it here. There’s plenty of awful prose out there; you don’t need my help finding it. Then I read the back cover. “THE STUNNING #1 BESTSELLER” it says right across the top. Then it lists several newspapers who listed the book as a top-seller. What!?! This book?

I’m stunned, anyway. I decided to write a little review after all, not so much to criticize the book as the system that allowed it to attain such stature.

Usually, even with books or authors I don’t like, I can understand at least to a certain degree how they became successful. Dan Brown’s not very good but he has excellent pacing and managed to anger the right people. This book leaves me baffled.

Some guy at Booklist says, “Totally gripping and downright impossible to put down.” Gripping? No. No it isn’t. The characters are boring, there is no escalation of the stakes (unforgivable in a thriller), no character growth, not a breath of humanity anywhere to be found in these pages. The criminal plot depends on the incompetence of the good guys. Potentially gut-wrenching scenes are glossed over so we can get back to the Perfect People for another dose of sentimentality. Not gripping. USA Today chimes in as well, along with Publisher’s Weekly and a handful of book-review Web sites. Did they read a different version? One without so much suck in it? Are these people even literate?

Don’t waste your time with this book. In fact, just to be on the safe side, stay away from Patterson entirely until he proves this was just a fluke. Probably best to stay away from books published by Little, Brown, and Company (responsible for the hardcover version of this fluff) or by Vision. Somewhere there is an editor who approved this book, and I want to make sure I never encounter anything else that crossed her desk. As long as we’re learning from the mistakes of others, it’s time to take Booklist a lot less seriously as well.

The only explanation for the sales that I can come up with is the name: James Patterson. Apparently he’s pretty famous. Bookstores will pre-order a lot of copies, which drives the rankings up, which drives sales by people who won’t even read the first sentence of the story before taking it home. If it weren’t for the big name, not many people would have read the second sentence of this thing. The few that were carried through the first part by the suggestion of sex would have bailed out soon thereafter.

Is Mr. Patterson concerned about protecting his name? It doesn’t look like it. This book can’t be good for his reputation, no matter what the sales were. (I am assuming that at some point he wrote good books to establish his reputation.) He can read, I’d be willing to bet; he must know this novel is junk. Eventually, people are going to hesitate to pick up his next title, after getting insulted by a previous purchase.

Ooo! Or maybe — just maybe, mind you — Michael Ledwidge knows something. Something James Patterson would rather not become public. You see where I’m going with this? Ledwidge wrote the book but somehow coerced Patterson into putting his name on the thing as well. Farfetched? It’s a lot more plausible than the story in Step on a Crack.

And can someone tell me what that title had to do with anything?

Note that as always, if you use the above link to buy the book, I get a kickback.

Observations Observations

Blogs and Bloggers

June 7th, 2009

Most blogs fail. Most of the rest should.

A Facebook friend of mine posted a link to a NY Times article about the high failure rate of blogs. I couldn’t read the article without registering, but that didn’t stop me from commenting. You don’t have to thank me; it’s what I do.

As I pondered the short life span of the typical blog, I decided that bloggers fall into a few categories, and failure can (usually) be predicted just by identifying what class the blogger is a member of:

  1. People with nothing to say. Unscientifically, I’d say this is the vast majority of blogs. Many of these blogs might better be described as journals; the content is really meant for the consumption of the writer, not any audience. After a few weeks, anecdotes about the crazy antics of Fluffy the cat get old. After a few months these stories get old even for the blogger and he quits. Some people have a treasury of a few really good stories, and those will keep them going for a while, but when the well runs dry the blog fades away.
  2. People who lack the skill to say what they want. I suspect that this group is fairly small, as most people who lack language skills probably don’t start blogging in the first place. The exceptions to this rule, I suspect (having done no research) are found in sport blogs and political blogs, where passionately held beliefs are undermined by the complete inability of the writer to express himself.
  3. Interesting, articulate people with unrealistic expectations. When the blog doesn’t become famous overnight and the blogger realizes she must devote time to it almost every day for months for it to have even a remote chance of catching on, they quit.
  4. Interesting, articulate people who embrace the medium and do it for the pleasure of doing it. They produce what we in the industry call “good blogs.”
  5. People who, despite having traits from categories 1-3, continue to blog, rehashing old material and catering to a microscopic audience. Even as readership remains constant for several years these writers delude themselves into thinking that their blog sucks less than most blogs.

On a purely unrelated note, as Muddled Ramblings and Half-Baked Ideas celebrates its fifth year of contributing to the noise of the blogosphere, the MuddledRamblings.com business cards I designed say at the bottom, “Sucks less than most blogs!”

Fundamentally, I think most bloggers want to be read. A growing audience is the payoff, more people reading, more people commenting, lively discussions triggered by the words of the blogger.  It seems obvious, but when it comes right down to it, most blogs are not read. Personally, I don’t read that many blogs, and comment on fewer still. There are just too many of the damn things. Blogs that don’t produce consistently excellent posts, with some thematic connection between posts, are not going to grow big audiences. (The exception to this is the celebrity blog, where people read just for the name.) I’d have a much better chance at a large readership if I wrote a blog strictly about software engineering on a particular platform rather than just posting whatever drivel pops into my head.

I just like writing drivel, is all.

Writing Writing

Writing I Read When I’m Feeling Bad About My Writing

May 29th, 2009
Every artist has ups and downs. Occasionally I do as well. How do I convince myself I'm not a hack?

There are times I look at the product I’m putting out and there’s just no pretending. It’s not that good. Other times I read something I used to think was good and it turns out to be a disaster of poor communication. At times like that, it’s easy to think I suck. Not just think it, to know it to the core of my being. I suck. Suck, suck, suck! Nothing I write is any good and I’m just wasting my life trying to make a living at something I suck at.

It’s not a pretty thing.

It’s hard to work when you are absolutely certain you suck. What I need at times like that is some glimmer of hope that maybe, sometimes, on the best of days, a brief moment of not-sucking is possible, a fleeting flirtation with not-so-bad that can fuel the hope I need to create the next hyperbolic, rambling train wreck.

A long time ago, on one of my first-ever golf outings, I hit a magically beautiful shot. Now I think of that shot as I search through the cactus for my wayward ball. Most of my shots end up in painful places, but there’s always that one… Likewise, when I’m scrounging through the rough trying to find any reason to keep working on a story and by extension keep working at being a writer, I think of the good shots I’ve hit in my day. Those are the stories I go back and read when I need to get myself back to the happy place.

I’m nervous when people around me are reading my work, but last year I was with my dad as he read “The Tourist“. “That’s really good,” he said. I’m not sure it stands alone; it’s better I’m sure if you’re familiar with other Tin Can stories, but I read that and it still gets me. I really like that story. Oddly, I have a hard time putting my finger on why. 

The story that started the series, that the good folk at Piker Press had to call to my attention, was “Tin Can“. It’s a simple story, but subtle enough it fooled me for a while.

Then there’s Crazy Blood. It’s been rejected, so maybe others don’t see what I see in it, but I read it tonight and I have to say that I am on occasion surprised at my own word choice. I haven’t the slightest idea who might pay me money for this story. Crazy Blood might appeal to no one but me, which begs the question of whether it’s an example of writing that demonstrates that I have what it takes to be a professional, but that’s OK.

A user of Jer’s Novel Writer sent me a message after reading “Serpent“. The title of the message was was “Holy Crap!” I was already happy with that one, but that unsolicited feedback didn’t hurt. It’s a cool story, a little clunky in spots I think now, but with a sweet conclusion. It will definitely and appear in my “Piker Years” anthology, after a couple of minor tweaks.

And the novel, The Monster Within, awaiting the latest set of revisions to make it something others can love as much as I do. I wrote the damn thing and I’ve never got tired of it.

Usually, when I’m feeling that every word I write is worthless drivel, I can read some of the above and tell myself, “no, only most of what I write is worthless drivel.” That seems to be enough to keep me going.

Reading Reading

The Three Books I’ve Read Written by Dan Brown

May 15th, 2009

This list will not grow.

As another big-budget movie based on a Dan Brown novel rolls out, supported by a massive marketing push, I’d like to share my thoughts on the three Dan Brown novels I’ve read, in the order I read them. I’m a bit surprised I’ve not mentioned them in this blog before.

I first encountered Dan Brown in a cluttered living room in San Diego. Angels and Demons was the title of the book, and my friend recommended it highly. I had free time, and reading is part of my job, so I sat down to consume it.

I’ll say this for the story: It was paced well. Events happened and knowledge was gained at a rapid pace but there was time for characters to reflect and for readers to catch up. It’s why I finished the book. The two main characters weren’t bad. And… that’s about it.

On the other hand, the science the entire story was based on was preposterous. The whole plot is driven by a battery that lasts twenty-four hours to the second, and it never seems to occur to anyone that a) battery life is not that predictable and b) even if it were possible to create a battery with a charge that lasted an extremely precise amount of time, there was no motivation here for the people who created the battery to worry about stuff like that.

That’s really a minor quibble, but everything else depended on it. People base decisions that could lead to the destruction of Rome and the death of millions of people to a blind faith on the 24-hour timer. It was the clock that drove the plot.

If that one seems ticky-tack, there were many worse errors in the grand parade of downright stupidity as far as science and scientists were concerned, creating an overwhelming wrongness that ruined the story. Things start off with a ride in a jet that can’t take off and go downhill from there. Then there was the tension between religion and science, which certainly exists, but the ability to create antimatter (which has been going on for decades now) certainly hasn’t created new rifts between science and religion. Unfortunately, this rift is another key plot driver. And the location of the secret lab at CERN? Nope. Antimatter as a world-changing power source? Sure, until you consider the ungodly amount of energy it took to create it. I could go on and on.

There was lots of information about some of the great works of art around Rome and the men who created them, and I found some of it fascinating. (Or was that stuff in the Da Vinci code? It’s a blur, now.) But was Brown’s research on art history any better than his science? I don’t know, but his credibility was shot long before the story even reached Rome. I just hope I’ve forgotten all those facts, in case they’re wrong.

And as far as the process for selecting a new Pope, I’m pretty skeptical that what is portrayed here – even if we allow that a bunch of senior church officials could be so utterly stupid – would be legit.

The ending is simply preposterous. Ridiculous. Eye-rolling, head-slapping stupid. But it’s dramatic, I’ll give Mr. Brown that.

Fool me once, shame on you. Fool me twice, shame on me. I don’t remember who convinced me that The Da Vinci Code: A Novel
would make up for my disappointment with the previous read, but I was reasonably optimistic as I started in on the most famous of Mr. Brown’s novels.

To be honest, I don’t remember that much about the book anymore. It just didn’t stick. I remember rolling my eyes a few times, and thinking “that would never, ever, happen,” but overall I was not as annoyed by this book as I was by the other. How’s that for a ringing endorsement? “Dan Brown’s least annoying work to date!” Some of the characters are reasonably credible, but others are cartoons at best.

This book was controversial, which ironically is probably why we’re being treated to multiple major films based on Mr. Brown’s work. Remind me to write an otherwise innocuous novel that says Jesus had children. (I think that was the controversy – I suppose I’ll have to come up with my own.) There is a “huge” revelation in the story that begs a large question for anyone who can count past thirteen.

Still, I read the book, and once again I think the pacing had a lot to do with that. Dan Brown, for all his faults, kept me turning the pages.

Fool me three times…

Then there’s Deception Point. A steaming pile of suck from beginning to end (yet, once more, I read it all). This book was off on so many levels there’s no point trying to list them here. Let’s just leave it at: I’ll never read a novel by Dan Brown again.

Note: if for some reason you actually want to buy one of these books, and you use the above links, I get a kickback.

Bars of the World Tour Bars of the World Tour

Solvent!

March 18th, 2009
It wasn't pretty, but my fiscal woes are at least mitigated.

Well, here I sit at Bowle & Bowling, listening to the rumble and clatter of the bowling balls, and a feeling of normalcy is starting to come over me. I can pay rent.

Even the last chapter of my adventure was not as straightforward as I had hoped. The credit card people told me, “you can get cash from any bank with a Visa sign on the door.” This, it turns out, is not true. Not at all. Not even close. What she should have said was, “It’s possible there’s a bank in Prague that will advance you cash on your card, but good luck finding it.”

I started my two-day quest in my own neighborhood, at the largest and fanciest bank. As usual in my neighborhood no english was spoken there, but we communicated surprisingly well. “I need money,” I said in Czech. I didn’t know how to say “cash advance” in Czech, and credit cards are so rarely used here that it wouldn’t surprise me if the bank lady didn’t know the word either. “You can’t use the bankomat?” she asked. “No, it’s an emergency card,” I explained. She thought for a moment. “I’m sorry,” she said. “I can’t help you. I don’t think any bank can.”

I canvassed the rest of the neighborhood and got the same story. It was getting late so I decided to try another approach. I would call my bank and see if they could issue me a PIN so I could restore all the happy ATM-ness to my card.

Naturally, that turned out to be complicated. Then my Internet connection went down, leaving me Skype-less.

Back on the street again today, an earlier start, knowing that I was going to have to go down to the city center to have any hope of success, and I would probably have to visit a currency exchange. There are plenty of them on Wenceslas square and thereabouts. I wandered up and down the street, window shopping. I noticed that the rates most places advertised were for very large amounts; the normal-human rate was much worse. Luckily (an odd sort of luck, I must say), I will be needing a lot of money, so I found the best rate at a 0% commission place and went on in.

After a little confusion because I said “hundred” instead of “ten” we got the deal squared away. “There will be a commission,” the woman said.

I thought of saying things like, “but your sign says…” but I knew it wouldn’t help, and I knew it would be the same everywhere. No commission on currency exchanges. Credit card: get ready to bend over. If asked they would probably say that they have added expenses and whatnot, and there’s a risk of fraud they have to factor in. In reality, it’s because people getting cash off their credits cards are all desperate schmucks like me. I was tired. I just wanted to be finished with this whole mess. I bent over.

This is officially the last time I think about how much I just spent to get my own money.

Now, no more worries! Now I have money, enough for me to cover rent and some of the expenses of filming, and I have time to find another conduit for the rest. Back on my feet, baby!

Bars of the World Tour Bars of the World Tour

The Waiting is the Hardest Part

March 16th, 2009
Soon I will have money again. But when?

Last Friday I finally got someone in the banking world to take up my cause. I really wish I’d got her name, because she was the kind of get-it-done person you want when you are hungry and all your money is tantalizingly beyond your reach. Hours later the call came from Visa: your replacement card is on the way!

Hooray!

She told me it would be delivered the next business day, Monday. I woke up this morning with the sun on my face (solved with a pillow), but then Real Life started to weasel into my thoughts and suddenly I sat up with a jerk and lunged for the computer. What day is it?

The answer: Monday (rhymes with today). I’m getting an express delivery today. I don’t know when.

I live in what is called around here a ‘villa’. It’s a big house built to have a family on each floor. My place is an afterthought; at some point someone realized that the attic was just a lost opportunity for rent. It takes me three keys to get in: There’s the iron gate by the street, then there’s the door to the building, then there’s my own door at the top of the steps. The catch is that someone on the street has no way to signal me to come down. As I type this, the delivery guy could be down there cursing my name.

So I sit now, windows cracked open despite the chill rain outside, waiting to hear the UPS guy. I am hopeful — when I talked to the final Visa operator I mentioned that the driver should have my phone number. “It will be in the information,” she said, “But we can’t guarantee that the driver will have a telephone.” That was the first funny thing that came out of this whole trauma. A czech without a phone. Ho!

But now I sit, my apartment getting colder (a little complicated – my only windows with ears to the street are in the bathroom, where my heater also lives. The heater pump is failing, and makes a racket. If I have the bathroom door open to hear sounds from the street, I can’t have the heater hammering away.)

So now, I wait. And hope. If the weather was nice I’d just take a book and a chair down to the front lawn. Alas, the weather is not nice. So I’m up here, afraid to do anything that makes the slightest sound lest I miss the critical delivery. Today promises to be big fun.

Bars of the World Tour Bars of the World Tour

Balaton

March 14th, 2009
In my current fiscal crisis I must economize. Is the sacrifice worth it?

The cheapest (large) beer at Little Café Near Home is now well over a buck fifty. My preferred beer is nudging up against two dollars for half a liter. Therefore I’m spending more time at the Budvar bar next door. Tonight, however, I stopped by LCNH to snag a bottle of wine. Tea, bless her heart, a fine and happy soul who understands that life is but a joke, redirected my eye from the 95-crown wine selection to the hungarian outlier. Twenty crowns. Today, about ninety-five cents.

It’s sitting on the table in front of me as I write this. I’m a little bit afraid. I will open the bottle tonight. I will drink at least some of the contents. It’s just my imagination I know, but I already feel the hangover coming on. But for science, it must be done. Wish me luck.

Bars of the World Tour Bars of the World Tour

Travelers Tip: Don’t Use Raffeisen Bank

March 12th, 2009
I'm sure Raffeisen Bank is a fine place to keep deposits, but they have hungry ATM's

I am still struggling to recover from having my bank card eaten by an ATM at the bank closest to my house. In fact, this is the second time it’s eaten my card, but the first time I had a backup. As my tale of woe spreads, I’ve learned that several of my friends have had their cards eaten by the hungry bankomat machines of Raffeisen.

My theory on the matter is that Raffeisen is more sensitive to fraud than other banks, so if the slightest thing goes wrong on the transaction (say there’s a glitch in transatlantic communication, or, as is the case with my bank, one of the card-processing networks that serves them goes down), that’s it – card eaten. For locals this is an inconovenience, for travelers it is a major pain in the butt.

So, while before I thought it was bad luck that my first card got eaten, now I know that there is a difference in banks, and I will never use a Raffeisen bankomat again. I encourage you to do the same.

Meanwhile the emergency delivery of a replacement card has been far less than swift. First told I could even have a card the next day, now it’s been a week and I’ve been riding a ridiculous merry-go-round between San Diego County Credit Union and Visa Emergency Services. My nerves got a bit frayed on the phone last night, as the credit union seemed to have gotten confused somewhere along the way about a check card I never activated and in fact don’t have. Sure wish I did. Or that I’d applied for a Paypal card. Or anything.

“I’m getting hungry,“ I tell them over the phone. (Thank the gods of telecommunication for Skype.) Now I’m waiting while (once more) Visa Emergency Services seeks permission from my bank to issue a new card.

So, lessons learned: First, don’t use Raffeisen Bank. Never. Second, don’t don’t count on two organizations to work well together. Hound them relentlessly until things are fixed. Third, don’t tell your landlord you’ll have the money on a certain day. I never thought I’d be the one tip-toeing past the landlord’s door. That’s out of a sit-com, right? Except that was me today. And just like in a sit-com, I got to the bottom of he stairs, realized I’d forgotten something, and tip-toed back up and down again. High comedy.

Observations Observations

The Language of Omission

March 9th, 2009
 

She was surprised when I mentioned that I knew she was sweet on the guy, but it would be pretty dang obvious to anyone who paid attention. I haven’t seen her in a few weeks since but she’s here now, sitting next to the man of her dreams, and he’s being friendly but is also being meticulously careful to not give the wrong idea. Case in point: she pulled out a cigarette, slipped it between her lips, and waited. No lighter came. That has to be a sad moment.