Object Orientation and Object Obsession

The last time I did any serious computer programming (apart from playing around with macros in different Microsoft or Corel products) was when I was in high school. Back then, BASIC was spelled in all capital letters and lived on computers that ran CP/M as an operating system, and still had line numbers:

10 Input a$
20 Print "Hello, " a$
30 Goto 10

I owned a TRS-80 Color Computer 2 from Radio Shack, which had 64K of memory (only 32K of which could be accessed at any one time), with no hard drive but a dual floppy drive. It’s fun to point back at that little device and chuckle fondly, thinking, "How cute they were in their larval stage", but, really, those machines could often be deceptively powerful. I wrote a large program in BASIC on that computer which kept track of all of my appointments and contacts, had its own (very simple) scripting language, made advanced use of randomly accessing data from the floppy disk that served as the data disk, and built display screens "on the fly", like modern active webpage schemes do nowadays. Even though it was slow (and got slower as the appointment and contact databases got larger), it was, I think, pretty advanced; I had figured out how to write programs in BASIC that were "modular" such that the subroutines were generalized enough to be re-used over and over and over by different programs (even though every single bit of a program had to be loaded into memory instead of accessed in parts from a disk); I was treating my data as objects, more or less, and even borrowing some tips I’d picked up from working with Paradox with my uncle one summer and making my database more or less relational instead of completely flat.

In short, I was awfully impressed with myself at the time, and I still am, when I look back on that program and others that I wrote like it.

In college, though, for some reason, I decided not to pursue computer programming at all. I wanted to be a doctor, and thought that I wouldn’t need to deal with computers at all. Then when it became clear that I would never be a doctor (nothing will help cure such delusions better than doing volunteer work with sick people and realizing that you can’t stand the whining — that, and flunking a class in basic organic chemistry), I still didn’t go back to computers. I stuck with my philosophy major and never really gave a thought to programming or computers. I enjoyed working with them when I did, but I never really thought about computer work as a career.

But now that I’m looking at a serious career change, from the world of a Human Resources administrator to the world of a computer nerd, I’m starting the process of learning how to program all over. My experiences in recent months with HTML, DHTML, JavaScript, Perl, and Cold Fusion have reminded me how much I enjoy sitting down and bashing out something that makes the experience of using a computer more enjoyable and useful for other people.

But programming has also changed considerably since my high school days. Objects? Methods? Threads? Superclasses? Instances? Packages? Interfaces? Huh? What? I’m not worried about being unable to pick up these techniques and terminologies, and I’m pretty confident that I’ll be able to do so pretty quickly. In fact, object-oriented programming is much like the predicate logic and modal logic that I used to play with in college. I’m just going to have to get used to the idea that when I want to do something in a program, I have to create an object to do it with.

Cue segue into a cheesy metaphor between computer programming and human emotion.

Object-orientation can be both a good thing and a bad thing. In computer programming, object-orientation is good, because it really does make things easier to do, and it makes playing with information a lot easier (in fact, I have recently discovered that there’s a new breed of database design, "object-oriented database management", or OODBM, which tries to treat records of data like objects instead of relating everything to everything else). In life, object-orientation can be either a good thing or a bad thing. It depends on what object you choose to orient on.

Some examples:

My fiancé’s object-orientation and obsession is towards cats. This is fine with me; I like cats and am even willing to sleep in the same bed with one or two of them as long as they understand that they’re not to approach my face (I’m allergic to cats, you see).

I, personally, have an object-orientation and obsession towards my career. Actually, I’m worried that it may not be healthy in some ways. I’ve sometimes found myself so obsessed with my future hoped-for career that I get overly upset about my current job, and even find my self-esteem wrapped up in it. This is definitely not good, as I come home from a day of work to my fiancé and whine at her about how my job sucks and how bad my prospects for future career development are. Fortunately, Jennifer is wise enough to know that I am not defined by my career or by how much money I make; and she’s even clever enough to be able to convince me of that too, at times.

Then again, there is at least one person in the world whose object-orientation seems to be focused on making me appear bad in my fiancé’s eyes. I am not a wealthy man, and I have debts, and I freely admit that up front. However, I certainly have no intention of having my future wife pay for my debts, I will never borrow money from her (nor did I ever borrow money from this other person that was not offered to me and that I did not pay back within a day), and if the unthinkable happens and Jennifer and I ever get divorced, I fully intend to leave our house with nothing but what I brought in to it. People who know me, fortunately, know that I am responsible and mature enough to own up to my own debts and that I am determined to pay them off on my own without anyone’s help, and my fiancé and I have discussed these issues on more than one occasion. Unfortunately, this other person’s object-orientation and obsession seems to be focused not only on making me appear bad to Jennifer, but to outright slandering me in public (without even doing me the courtesy of leaving out my name, as I have left out theirs). It hurts me, but it also hurts Jennifer. It’s an instance in life where object-orientation is a bad thing.

Okay, I admit that this metaphor is stretching things a bit. Fortunately for me, I have never claimed to be a literary genius, which lifts from me the burden of making sense to you, my three or four devoted readers.

But I’ll draw forth another analogy here, which harkens back to my May 22, 2000 Letter to Jennifer; when I was 18 or 19 years old, I figured that I know everything there was to know about relationships and the human heart, just as I thought I knew everything there was to know about procedure-oriented programming. Nowadays, I know that, just as programming is a hell of a lot more complicated than I had ever thought it was, the mysteries of the human heart and its vagaries are a lot more complicated than I had even suspected back then. And now here I am, making a career change into a new field that I thought I understood, and making a significant life change — from single to married — in my own heart, which I also thought I understood. I don’t understand either programming or relationships as well as I thought I had, but I am enjoying the process of ex
ploration, discovery, and learning. All over again


Over the past three or four years, since I decided that I no longer wanted to be a delivery driver, I’ve been focusing my career in an administrative direction: the plan was that I would start as a basic administrative assistant at UC Davis, then move up the ranks to become an administrative analyst, helping the University function on a day to day level. I saw myself as a department manager, perhaps even a vice chancellor or something someday.

At this point, of course, I have no desire to move in that direction. In fact, I doubt that I’ve been interested in it for a couple of years; I haven’t even tried to make any progress in the analyst direction, in spite of several opportunities to do so. I think that working in Labor Relations has helped me in this regard; seeing how badly management and employees are capable of treating each other has made me realize that there are many messes I simply don’t want to get into, and as an analyst, I’d be thick in the middle of them. And, so, about a year ago, I decided to move my career in a technical direction.

Of course, being an administrative assistant can be awfully comfortable; and my position was extremely comfortable, as my supervisors and managers seemed very willing to let me explore my technological inclinations as long as my "official" job got done. So while I thought about moving in a technical direction, I never felt a strong need to pursue it very aggressively.

As the one or two of you who read this journal on a regular basis probably know, the urgency for me to find a new job and get my new career going has suddenly skyrocketed. My revised position description contains no technical responsibilities whatsoever, so my comfort level has vanished. It’s now vital for me to develop a plan for getting a new job and for developing the skills and contacts that I need in order to get that new job.

The first step of the plan is obviously to set a goal. With a goal in mind, it’s easier to point yourself in a direction and, with help from as many different people as possible, develop a specific course of action which can get you from where you are to where you want to be. This afternoon, I sat down, gave it some serious thought, and came up with the following (based on where I’ve been focusing my learning and interests over the past year or so):

Career Goal: To find an exciting, challenging, and rewarding job as a database/web developer, paying at least twice my current salary, for a large, socially conscious organization, within one year.

Part of the plan for achieving this goal is to get as much practice in doing these things as possible. Fortunately, today, I was able to take a step in that direction. I received an e-mail from a professor at UC Davis who is interested in having me help him with a web-based project which would allow students to virtually explore the ruins of Rothchild Castle in England. I’m excited about this project, because I can utilize many of the skills I have already learned, and it will give me a chance to learn many new skills.

Here’s where the irony comes in.

This same professor was formerly the chief representative of a labor union at the University; and my current job involves helping the University cope with the labor unions. So now I’ll be working for this professor. Well, okay, maybe the irony is lost on other folks, but I think it’s there.

Of course, I keep thinking to myself, if I had been focusing on this sort of learning for these past four or five (or ten) years, I would be well-established in my technical career by now. This, of course, is a pretty useless mode of thought, since I wasn’t even interested in this career field four or five years ago. But, being the impatient sort of person that I am, I want to be in my new job now! Ah, well. Patience, I suppose, is something that I need to build up.

That mode of thinking — that "if only" — certainly isn’t limited to just my career; it’s present when I think about relationships as well. I found myself thinking, several months ago, that I should have followed through with certain relationships, taken certain up certain women on the offers of relationships that they had offered, and so on. And as I think about my upcoming marriage to the most incredible woman I’ve ever known, I found myself thinking: "If only I’d been looking harder before or if I’d followed through on certain offers before, I’d probably be married by now."

That last part is probably just as true as the statement that if I’d focused on technology five years ago, I’d be in a comfortable job by now instead of my secretarial job. On the other hand, if I’d gotten myself married years ago, I would not be getting married to Jennifer in a year; and in all honesty, I can’t see myself as happy sharing my life with anyone else. If I’d gotten married years ago, I would be unhappily married now; these things take time, and they have to happen at the right point in your life. I’m not a person to use terms like "fate" or "soulmates" or anything like that; but I’m pretty certain that if Jennifer and I had gotten together even just a few months ago, it wouldn’t have worked out.

So to talk about my career the same way probably carries the same irony; changing careers four or five years ago would probably not have worked out at all, but changing careers now is definitely the right thing to do.

Fortunately, though, just as I’m on my way to marrying "the one", I know that I’m on my way to the career I’ve been looking for. It’s going to take me awhile — I have no illusions about that — but I’m on the way, and I feel good about it.

And, as always, I’m always open to suggestions and ideas. Feel free to send me e-mail if you have thoughts, ideas, or suggestions.

My Parachute Just Exploded

Note: I’ve finally gone and changed the look of this journal. I personally thought that the pop-up windows for each journal entry were cool, since I wrote the JavaScript myself that opened them and allowed the viewer to manipulate them. Unfortunately, too many other people didn’t think that the pop-up windows were cool, so I’ve decided not to use them for future journal entries. The archives will still have the pop-up format until I get around to fixing them (about the same time that Hell freezes over, I imagine), but future entries will be formatted like this one — until I change my mind again.

A few months ago, the acting manager of the Human Resources division at UC Davis announced her resignation; and in the wake of her resignation, which came shortly after a massive organizational review by the KPMG Management Consulting Company and a severe budget crisis, it was announced that Human Resources would be re-organizing completely. The new structure would be lean, mean, tight, financially stable, and tremendous fun for everyone. Not only that, we were promised, but everyone within the division would have the opportunity to let their own talents and skills shine, and everyone would be happy.

Generally, I try to be an optimist. When the above announcement was made, I tried to believe it; I tried to believe that I would get a chance to shift into a more technology-oriented position which would include web development and database development, without having to go through the hassle of actually looking for a new job. And when my unit was subsumed into a larger "super-unit" consisting of our group and two others, I was told that I would be the primary technical support person, the webmaster, and the database consultant (in liaison with Human Resources Information Services). I was invited to submit my own position description and I excitedly set about writing one up, tossing all of the secretarial functions I still had to other administrative assistants and taking on all of the technological and database/web administration duties that I knew would ultimately move my own career forward at a careening pace.

Unfortunately, it seems that it’s the cynics who rule the workplace.

Yesterday, after all these months of restructuring, promises, and solicitations of my own input, I was finally given my new, revised position description. I can’t help but wonder whether my ideas and desires and talents were all written down on a list and then burned or possibly pulped, or perhaps even lining a litter box somewhere. Not only is there no mention of database and web development anywhere in the position description, but any hints of technical support are gone as well. Nothing remains but a brief token nod to "report generation" and "data maintenance." Instead, my position is nearly 100% administrative support: I went from being a technical support coordinator, webmaster, and database developer to secretary. It’s as if all the months I spent fixing broken computers in the unit, building applications in Access and Cold Fusion to let the manager get the data he wants when he wants it, and developing the unit website were completely ignored.

I’ve been trying desperately to figure out the motivations behind this. I’m told that it isn’t punishment for anything (though I’m not certain I can see what I would be punished for anyway); all I’m told is vague mentions of "business necessities" and so on. What I’ve concluded is that this is driven primarily by ignorance. My tech support duties have been removed because Information Services is supposed to handle these duties; my webmaster responsibilities have been removed because Information Services is supposed to handle them. Of course, my own conversations with the manager of Information Services lead me to believe that Information Services would like nothing better than to have a distributed network of technical support people and web developers so that they don’t have to tax their own very limited resources. On the other hand, perhaps that, too, is as empty a statement as, "Richard, I’d like your input on the development of your new position description."

And my own emotions surrounding this development have been pretty strong for me. I feel hurt, certainly, but also betrayed, ignored, and disenfranchised. Why did management bother asking for my input if they had never intended to use it? I found myself so upset at the entire situation that I couldn’t concentrate on my work. I told my supervisor that I was going home, and I left. Later, at home, I had a conversation with a friend of mine who works in the same office, and she suggested to me that I take today off as well; she even talked to my supervisor on my behalf, which I really appreciated. I’m feeling less upset today, but I’m certainly not happy about the situation.

What really bothers me most about my own reaction is that I find it very difficult to build up any concern anymore for the unit. I want to be a good employee and contribute to the unit; I want to be able to do my best and give my all and feel committed to the work. Unfortunately, it’s not happening. In its place I’m feeling nothing but indifference for the unit, its management, and the work it does. I find that I have no motivation whatsoever, and no interest in doing good work. This is bad not just for the unit but for me as well. It’s going to be a drain on me, and it’s going to hurt my career in the long run.

What I’m really getting out of all of this is a voice from God saying, "Get the hell out of Human Resources now!"

So the urgency behind building a career as a web developer and database developer has skyrocketed. I still don’t know how to start doing it, really, but I’ve taken the plunge by contacting potential employers, revising my resume, and developing a plan for learning Java, Access, and working on how I can learn Oracle and a few other tools and development applications. Ideally, of course, I’d slip right into a high-paying job that would pay me at least twice my current salary just to learn all of this, but that’s not terribly realistic. I’d also like to start this new job this coming Tuesday, but a realistic job hunt timeline is at least four to six months; and since I’m looking at an entire shift in career, the process will probably take me even longer.

I find that my emotional state is very mixed. On the one hand, I have never been this upset over a job-related situation before; I’ve never had to actually leave my workplace because I was feeling upset. I’ve never had to take a day off because of stress or burnout or frustration. And yet, here I am.

And yet, at the same time, I’m feeling happier than I ever have in my life.

The latter emotion is easy to figure out. I’m engaged to the most amazing woman in the world (see my May 22, 2000 entry: "Letter to Jennifer"). And looking at her, I know that she is one person who will never abandon me or abuse my trust; and I know that if she wants my input on something, she will actually consider it. I can trust her, and I know that she’s good for her word.

As I push forward in my career hunt, knowing that I need to be more aggressive with this hunt than I have ever been in my life, my natural reaction is to get discouraged. There’s so much that I don’t know, and the market is rather competitive, and I don’t have the overwhelming experience that would give me a strong edge.

But Jennifer tells me that she has faith in me. She tells me that if I put my mind to it, I can get that dream job, using the skills I enjoy using in a workplace that I believe in. She has faith in me.

And looking into her eyes, I know that it’s true.

Letter to Jennifer

Are you to blame for these massive changes in my life, for the sudden disruption in my life’s direction?

When I was 19, I was pretty sure I had life all figured out. I knew what love was, I knew what relationships were like and how they worked, and I knew precisely what was wrong with all of my friends’ love affairs. Never mind, of course, that I had never had a serious relationship of my own up to that point; I knew everything, and nothing was going to change that.

Of course, by the time I had turned 32 just a few months ago, I realized that what I knew about love and relationships amounted to very little. There’s no better cure for arrogance on these issues than a good dose of reality: my previous two relationships, while not outright disasters, had proven, ultimately, to be errors in judgement on my part, and with one or two outright calamities in there for the fun of it, I realized that relationships were a lot more complicated and love a lot more mysterious than I had ever thought.

I’ve had good relationships in the past; I dated one woman for more than five years and had a great time, though I never considered spending my life with her. And one other woman I ran away from when things got too serious and too good. I’ve thought, in the past, even while with other women, that I should have stuck it out with someone else, maybe thought that I could have been happy with so-and-so, or maybe I would have learned to tolerate being with whats-her-name for a lifetime.

Finally, I just figured that relationships and I should simply leave each other alone, and that the love I needed in my life was simply the love of good friends and close family. I was fully prepared to spend the rest of my life as the crazy (but cool) single uncle to my niece, the somewhat eccentric godfather to my godson, and a good family friend to those friends of mine with families. At the end of my life, I had planned to be one of the doddering old coots playing chess in the park with the other doddering old coots, never married, generally friendly and smiling and willing to play chess with the kids as long as they would put up with me ranting about damn modern music and the government.

That was my plan. That was what I was counting on. I knew that I would be content with my life like that, that I would not feel lonely as long as I had friends and family that I loved and that loved me, and I simply didn’t feel that I needed anyone to make me feel complete. I was already complete.

Now, you’ve come along, and all my plans have changed.

I’ve known you for over two years. That whole time, I’ve been attracted to you and I knew that if we had a chance we would make a great team. Sometimes I would be involved with someone else and I would be happy with them; sometimes you would be with someone else and I would be happy for you as long as you were happy. But then there was that night when it was just the two of us, at the end of a busy day, watching a movie and enjoying each other’s company. It took every ounce of nerve I had to kiss you that night; and words simply don’t exist to describe how amazed, shocked, thrilled, and happy I was that you kissed me back.

Sometimes I still reel in memory of that first moment: you kissed me back.

Everything clicked and came together; like a new sound card fitting perfectly into a slot on a motherboard, or a protein binding with the right enzyme, or a picture puzzle piece which fits so perfectly with the mate that you can’t even see the seam. That’s how I felt at that moment; that’s what I had sensed all that time that we knew each other; and that’s how I still feel now.

Asking you to marry me was the biggest risk I’ve ever taken in my life. I knew how you felt about marriage: how it scared you, how you always told me that you thought the best marriage would be in a duplex, and so on. And I knew how I felt about asking someone to marry me when I hadn’t even been dating them for a full year. I knew that our friends and families might be dismayed and that some of them might even try to talk us out of it. I knew that you would probably say no, and that the "No" would be there between us forever after that.

I asked you anyway, though, because I know that we belong together. You’re the intelligent, funny, witty, stable, positive, beautiful woman that I had always dreamed I would be with but never dared believe I would find. I knew you would say no, but you said yes. And I’m still reeling from that. I’m still expecting to wake up and find that I’ve never known you and that you were nothing more than a perfect dream; or that someone’s slipped me some drug into my coffee, and I’ll wake up strapped to a bed in rehab somewhere in Vacaville, and when I ask for Jennifer, no one will know who I mean.

I know that our marriage will not always be easy. I have seen people who were married and who were still in love with each other but who still had fights and bad times. I know that there will be times when we’ll be awkward with each other, that we’ll be confused, that there will be misunderstandings and fights, and that things won’t always be smooth.

But I also know that we will find ways to handle these problems. I don’t mean to reiterate the tired cliche that says, "Love will find a way"; but I do know that you and I can talk about these things, that we can work them out, that we can solve our problems. I get to spend the rest of my life with you, my love, and I can’t imagine anything better than that.

My Parachute Has a Great Big Hole

I have to confess: I really don’t care for my job all that much.

Surely, not liking my job puts me into a tiny little minority of American workers. After all, doesn’t 99.9% of the American workforce love their jobs? Well, no. Some studies have shown that something like 70% of Americans just don’t like their job, and that a significant majority of that 70% — something like 85%, I think — feel that they are simply stuck in their job with no hope for advancement or improvement.

That I don’t like my job that much is nothing unusual. But why don’t I like it? After all, I have great co-workers that I like and that I have a lot of fun with. My girlfriend can even attest to that. I also believe that the work I do is important work, since it helps keep the University running (even if I do occasionally feel that the whole point of labor unions in California is to deliberately waste my time). The money I earn is somewhat decent, though I won’t be buying a house or a car or anything like that anytime soon — especially when I’m still paying off some large debts and putting away 20% of my income each month to save for my trip to Europe. And the benefits — medical, dental, etc. — of working at the University just can’t be beat. Free medical coverage with no deductible and a small-ish co-pay, free dental (with no co-pay), free vision, legal insurance, a nice retirement package, and so on.

So what’s wrong with my job? Simply that it’s dull. It was a challenge when I came on board almost three years ago, when I found University personnel policies and labor relations fascinating. But once I figured out the rules of the labor relations game — that for every stupid manager there is at least one psychotic employee, but that people in the work force are, surprisingly, mostly stable — I realized that I didn’t find it at all interesting anymore. I do believe it’s important — after all, in large organizations, the Labor Relations unit (if it’s run properly and the people there know what they’re doing) can keep the workplace stable and healthy. And it’s gratifying that I work with people who do care about this stuff, and honestly do their best to keep the University functioning well. But I’m not one of those people, and it’s beginning to wear me down.

On the other hand, though, I am starting to delve into areas that I do find fascinating. Web development, for example, and database design. Last week I started learning how to program in Cold Fusion to create websites that are dynamic and which pull information from a local Access database — my first application was well-received in my department and I’m trying to get the go-ahead to build more. And just last night I wrote my first Java applet (it’s not exciting, to be sure, and does nothing more than print a silly phrase on the screen), and I found that Java is surprisingly easy to grasp. Object-oriented programming is going to take a little getting used to, but I don’t think that my brain will melt when trying to figure it out. So, needless to say, I’m very excited about the possibilities of building dynamic web pages for inter- and intranet use, with Java, Javascript, Cold Fusion, and MS-Access, or whatever. I’ve even coded XML, and find that fascinating as well.

But at the same time, this is all very daunting. I have all of these books on Java, JavaScript, HTML, XML, Perl, Cold Fusion, and Access, and they all fill up at least two feet of bookshelf space. It’s exciting stuff, but the amount that I still have to learn seems overwhelming at times.

And, of course, there’s the question of employment. I could probably find a stable job with the knowledge that I already have under my belt, but probably not anything that would match what I’m earning now. I haven’t got nearly the skillset I need to find a job that pays what I need to earn to keep myself afloat, let alone buy the house and the car and the Palm Pilot and so on and so on and so on. Until I can get paid to learn what I want to learn while still contributing to something which I feel is valuable, I am stuck doing this on my spare time and writing up small useful applications here and there to impress the socks off of my co-workers.

While it’s easy to get depressed over this, I find that I’m not. Sure, I’m a long way from the exciting high-paying job where I travel to dangerous parts of the world and solve tough database/web development problems, Indiana Jones style, and it’ll probably be a couple of years, at least, before I can seriously think about getting there. But, on the other hand, I’ve managed to get places before that seemed daunting and impossible. When I first graduated from college, it seemed downright impossible that I would ever find a good job at all, let alone one that would give me decent benefits and where I might have a boss who does, in fact, support my efforts (as much as she can, at least, without sacrificing the needs of the unit). I once thought that I would never own a car of my own. And even less than a year ago, I was nearly convinced that it would be completely impossible for me to ever be involved in a healthy relationship with a wonderful, stable woman. But all of these things happened, so, in all likelihood, I can probably improve my job situation as well.

Until then, though, I’ll keep fobbing off less interesting responsibilities of my current jobs onto other administrative assistants who find the idea of using the University’s centralized accounting software really, really exciting (while I myself find it tedious and mind-numbing), or who live for setting up meetings. And in the meantime, any ideas you might have for helping me develop my web development/database design career would be more than welcome.

Until next time, I remain,
Your obedient and humble servant,

P.S.: Shortly after posting this journal entry for the first time this morning, I received a telephone call from a recruiter who had seen my resume, and who was recruiting for a web development design position in Sacramento, which would use some of the very skills that I’ve been developing recently. The Universe excels at irony, and this is just one more example. Please keep your fingers — and whatever other digits you find helpful — for me. -RC

P.P.S.: And very shortly after posting my P.S., above, I received another call from another recruiter. This is simply too weird: two recruiters calling on the same day that I post my whiney job-hunt-related journal entry. I turned the second one down, though, because it is a Unix-heavy position down in Menlo Park; and I am certainly not any kind of a Unix guru (I’ve used "vi" and "chmod" and that’s it), and right now I have a vested interested in staying in the Sacramento area…

…And They Let Me Keep the Hose

As part of the weight loss program I’m in through the hospital, I went in yesterday morning for a "Basal Metabolic Reading". This process lets you see how many calories your body burns in a day just by being still, or by lying down and sleeping all day.

It works like this. You lie down on a bed in the back room of the cardiology unit, next to a huge cylinder. The cylinder is transparent, and inside of it is a bellows which rises up and down; it looks like part of the set from one of the old Mike Hammer Frankenstein films: Frankenstein Must Die(t)!, possibly, or Death to Adipose Cells!.

Next they hook you up to this device by a long plastic hose. Your nostrils are clipped shut, and a nozzle is inserted into your mouth. Then you breathe. In and out. As you breathe, the bellows expands and contracts. This is pure oxygen you’re breathing in now, folks, 100%. I’ve done it before, when very bad asthma attacks kept my lungs from doing their job. Pure oxygen is dry stuff, and after fifteen minutes I had a really bad case of cotton mouth.

Now, somehow this Hammer device measures the oxygen that you breathe out, and calculates the percentage of oxygen that your lungs absorb. And somehow, this number will let the machine determine how many calories per day your body burns in a resting state. The trainer explained this to me and I found myself thinking that it makes a great deal of sense; in my college days, I took at least one course in human physiology, which included a section on energy production. Oxygen is part of the process by which your body converts fuel to energy. Or something. Anyway, in my own case, if I were to spend the day in bed, not moving a muscle, barely even breathing, my body would still burn about 2,000 calories per day just to keep essential functions such as digestion and neural activity going (though I suppose there are some who would claim that if all my neuronic processes stopped, no one would notice the difference; to them I say, "Very funny, Mom").

I know you’re thoroughly fascinated by this already, but now here comes the really interesting part. During the two years that I was out of the Healthy Weight program, I managed to gain about 30 pounds (I’m not ashamed to mention that, especially since more than half of that is gone again). The trainer and I decided to conduct a little mental exercise to see how many calories, total, I had consumed during that time; since a pound of fat is about 3,500 calories, we worked out that I had managed to consume something like 105,000 calories above my daily maintenance level. Or, an average of only 14 calories per day above my basal metabolic rate.

Fourteen calories. That’s something like a single potato chip. Can you imagine that a single extra potato chip consumed every single day for two years can add up to thirty pounds in weight gain? Is the human body incredible, or what?

Of course, your body doesn’t burn just that basal metabolic rate each day. After all, your days are filled with walking around, working, typing, possibly even exercise, which bring up your daily burn by a few hundred calories. And if you work out, you can burn even more. The whole point of this program I’m in is to create a deficit between the number of calories that you burn in a day and the number of calories that you take in. Now if you lead a really sedentary lifestyle, like the one I’m trying hard to shed, you can’t afford to eat a whole lot; but if you lead a very active lifestyle, it’s easier to create that deficit, and lose weight.

And, of course, as you exercise more, increasing your lungs’ efficiency and your heart’s strength, your basal metabolic rate will actually go down. Especially if you lose a lot of weight: just carrying your bulk around gives your legs a good workout every time you walk to the bathroom.

So I got my Basal Metabolic Rate read. It was an enlightening experience, and I learned quite a bit. And because God only knows what kind of germs I breathed out during the process, they even let me keep the hose that I was connected to the cylinder with. It’s sitting in a big plastic bag in my car even as I write this, awaiting a time when I will come up with a practical use for a six-foot translucent hose with a mouthpiece on one end. Suggestions are more than welcome.

The Best Way to Experience Northern California

What can I say about Sunday that hasn’t been said here, here, and here? It was one of those days that you expect will start out one way, and ends up another. In this case, I had expected to have a miserable time, because I, personally, hate moving with a passion: there’s got to be a better way to spend an afternoon than lugging boxes and furniture around. Usually I help out if asked because the people moving are friends of mine, and they’ve promised either to feed me or to give me beer for my troubles. Those of you who know me already know that promising me good beer (not something like Michelob or Budweiser — contrary to what the advertisers would have you believe, most American produced beers are simply not beer; in fact, I’m certain that if you sent a pint of Miller Genuine Draft to a laboratory for analysis, the results would come back saying something like, "Your horse has diabetes." Guinness counts as beer; I like beer you can eat with a fork) is a good way to get me to do something. But in this case, the people moving were people I didn’t know, there was no mention of food, and nearly every single one of the people I was going to be with that day takes a perverse pride in declaring, "I just don’t drink beer". This is usually said with a haughty sniff, a tone reserved for the cultural elite who usually consider themselves above, say, Shakespeare or Thomas Pynchon, and who claim to have never heard of Star Trek.

So, why did I agree? Probably because Lisa IM’ed me and said, "Hey, Richard, can you help my friends move? Your girlfriend already said that she would."

Yep. Lisa blackmailed me into it. Pure and simple.

Okay, no, not really. But as I was lugging the umpteenth box of heavy hardback books (with lead covers, I presume) up the tortuously narrow — quite attractive — staircase, I found myself wishing that Lisa had blackmailed me into this. That way I could have said, "Hey! You made me do this!" And, I admit, my temper did get stretched a bit thin a couple of times.

But, you know, it really wasn’t that bad. My friends have mastered the fine art of amusing themselves under the most trying circumstances, and I like to think that I’m pretty good at it myself. Mishaps became adventures, and the day we spent in the rain moving perfect strangers ("Nobody’s perfect," my mother reminded me later that night) from Oakland to Berkeley is now the stuff of legends.

At one point, for example, Lisa’s new "housemate" (Lisa is very firm about this point), Michael, managed to vanish, just as we were about to try moving the couch upstairs. A search of the new apartment — small as it is, the apartment is riddled with dozens of hidden nooks and crannies, and it reminded me of something out of a Clive Barker novel — revealed that Michael was literally in the closet. He’d gone in to look at something, the door had shut behind him, and there was no handle inside. Apparently he’d been stuck for something like ten or fifteen minutes before he was finally rescued. After the inevitable joke about being "in the closet" had died down, Michael finally showed his face to us again, looking somehow wiser for his experience.

And I got to experience a moment of self-righteousness, which I always treasure. When a dolly full of books that I was leading down the ramp of the moving truck fell over onto the asphalt, and everyone else was still dry and safe in the truck laughing at me, I was able to say, "I’d just like to point out that while you’re all laughing at me, I’m the only one who’s actually moving anything at the moment." I live for opportunities to feel morally superior to other people, so I felt very pretentious and proud of myself as the laughter of the others simply increased in volume and derision. But at least I knew that I was in the right. Moral superiority is a lonely call, sometimes.

At the end of the day, some of us discovered that we had musical talent, or at least claimed to; between the wind instruments, the percussion, and the name of an ex-Beatles wife, we found that we could form the Yoko Ono Double-Oboe Bongo, Bones, and Whistle Band. Our first album, Can’t Get Enough Coffee (featuring "The Prig Song", which Lisa can’t get enough of), will be out sometime in the next fifty years. Our band sang loudly and proudly as we left Oakland for Mountain View, to indulge in some of the best sushi in Northern California, and then on the way down to San Jose to drop off Lisa and her new housemate.

Things became more sedate after that, as the new girlfriend and I decided to swing by and visit my parents (who live near Lisa) and my sister (who lives near my parents), discovered that various emotions can ooze out of one’s various orifices like various substances (pride, for example, oozes out like mint jelly), and had a quiet drive back from San Jose to Davis, thus completing our circuit of Northern California.

We had originally planned to go to San Francisco this past Sunday, to play and hang out. At one point during the move, while I was finding myself sprawled on the stairwell with a couch in my lap, I asked myself whether I would ever let Lisa plan another day in the Bay Area for us again. And looking up at all of my friends and feeling overcome with giddiness, I realized that I certainly would. Anytime.

Until the next time, I somehow manage to remain,

Note: For other perspectives on Sunday’s adventures, check out Thursday’s Child, Lisa’s Journal, and Jennifer’s Journal. Most of what they say is true. Most.