For obvious reasons, this blog went off to the wayside for quite a while.
Most of last winter, frankly, sucked. Loss, emotional upheaval, and generally, life. However, despite my well laid plans going awry along with the best of them, life moves on. My life in particular, has moved on at a heck of a clip through the end of last Winter and Spring.
In honor of all that life going on, I thought it seemed like a good time for a Spring re-cap as we approach the official start of Summer. (June 21st this year if anyone cares)
Once the new year rolled around, in the wake of our loss, my wife and I redoubled our efforts in searching for a new home, and in fact, as I type this, I'm sitting in our new home. As it would happen, I'm sitting in an actual office while my wife watches a movie in the living room. (She may or may not be watching Wreck-It Ralph, and I may or may not pause for 90 minutes to go watch it with her. I admit nothing)
A lot of folks will tell you that you shouldn't make big life decisions while grieving. The standard line being something along the lines of not having a clear head while overwhelmed by emotions and so on. To be honest, I can't argue. There were moments along the way when I hesitated, wondering if we were rushing, buying at the wrong time, or just buying the wrong house. As it turned out, we ended up in a home we're very happy with, for which we paid a good deal less than the appraisal, and well within what we can afford.
The home buying process is more than a little nightmarish for the uninitiated. I'm told, by every person I know who has ever bought a house, that our purchase process went quite fast. 31 days from our initial offer to keys in our hand. All I can say to those people is, "thank God, because I'd have lost my mind if it took 6 months."
If I could give you one piece of advice before you begin the home buying process it would be this: buy a decent quality scanner, and make sure that both you and your spouse know how to print, sign, scan and email back. One of my coworkers bought a house recently, and instead of scanning and emailing, she and her fiance ran back and forth across town every time the mortgage broker needed another piece of paper, which happens more often that most people use the toilet.
In short, buying a home is an awful lot of work. Granted, we can watch a movie, listen to music, work, exercise, and generally enjoy our lives without having downstairs neighbors pound on their ceiling because we made half as much noise at they make every Friday night. No more pot smoke wafting up from the next balcony down, no more incessant road-noise.
Most importantly, space. Blessed, wonderful, we're terribly grateful for it space. We have a modestly sized home on a very small lot, but it's so much more space than either of use has had in years that it feels like being freed. We've actually had a dinner party with two other couples. In our old apartment, if we'd wanted to have 4 adult guests, plus their kids, join us for dinner we would have had to set up a table in the apartment building's parking lot.
Of course, I also have a sunburn at the moment because... well...
...because I'm bald....
...but also because while buying a house is a lot of work, it's nothing compare to owning one. Today I mowed, edged, repaired a broken sprinkler line, replaced a hose-bib (which I may or may not have been the one to break in the first place), fertilized the lawn, pulled weeds, sprayed other weeds, attempted (with a success rate of 1:4) to repair some LED garden lights, and unearthed half of a flagstone patio that the previous owners had allowed to be swallowed by dirt and ground cover.
All of which is wonderful.
Seriously. It's pretty great.
Despite appearances to the contrary, such as my love of computers and the size of my pants, I'm really not an indoor kid. Spending an hour pulling up weeds or mowing the lawn is just about heaven for me.
I know a few folks who resent every minute they spend working on their homes. One coworker in particular comes to mind, and it's no coincidence that in the same conversation in which he tried to tell me that buying a house was the biggest mistake of his life, he also told me how awesome Grand Theft Auto 4 (4?, 5?, 27?, who can keep track?) Honestly, people, you don't need any video game that has, "hooker mode," as a feature. I can admit that I occasionally spend a little time now and then playing video games, but you can rest assured that none of the video games I play provide you with the option of hiring a hooker, and then give you the choice of either paying said hooker, or dragging her out of the back of your stolen car and beating her with a bat. Congratulations to Rock Star Games, for lowering the lowest common denominator of modern society by making a popular video game franchise that revolves around committing crime, and has the option of creating a character who is a modern day jack the ripper.
Anyway, enough of that rant for this week...
One of the big pieces of the puzzle for anyone who is trying to Grow Up™, is of course, their career. Only days after one of the most heartbreaking events in either of our lives, my amazing wife started a new job working for the Department of Human Services. It's not an amazing, fun-filled, challenging, ideal career sort of job, but it's a foot in the door of a place where she can eventually do fulfilling work that matters. It was a small, but very worthwhile, step back in terms of pay, placing her on a much better path. Now that she's there, there are an awful lot of very promising doors waiting to be opened.
That brings me to last piece to address in my spring re-cap: my ongoing quest to find myself in a better career. Sadly, the only success I can claim is that nothing in my working life is any worse than it was 5 months ago. Amazingly, when you stack up multiple major life events, it can be a little tough to find the necessary motivation to make the big changes for a little while.
Of course, I've got plenty of motivation at the moment.
First, I've hit the salary cap for my position. It's one of the down-sides of being hired well above the usual starting pay for a position; you're that much closer to the salary cap. So, instead of annual raises, I get a tiny token-bonus each year. Yay me. Of course, I've had some excellent nudges.
I've been working on a project at work which is so far above my pay grade, that it truly is a joke. My Assistant Manager wanted a tool for tracking a variety of pieces of information about our group sales for the hotel. Not a terribly complex sort of job if you have the right tools, so I told my Assistant Manager that I really needed MS Access to get the job done, and she passed it along to IT. To make a long story short (too late, I know), the IT manager refused, because it wasn't a necessary tool for me to get my job done.
You see, there's something in the IT industry called the "principle of least access." The concept is pretty simple, and on paper, it makes a lot of sense. The basic idea is that you give each employee the very least amount of access that will allow them to get their job done. For example, if you have an employee who doesn't need any more internet access than the ability to communicate with your credit card processing company at a specific address over a specific port, then you can lock out the entire internet except for that one connection, and more or less eliminate the risk of getting a virus from the web.
The trouble with that principle however, is that once a company gets over a certain size, usually when you start having people working in IT with terms like "Manager" or "Director" in their title, there's a good chance that the person making the decision about what exactly is the "least access" that will allow you to do your job, generally has no clue what you really need.
If you find yourself in a position like I'm in, where I'm overpaid for my official title because the position I'd really fit doesn't exist, you can get yourself into a place where the person deciding what you can and can't have access to, not only fails to understand what your official job really needs, but totally fails to understand what you need in the real world.
So, having been refused access to Access, I wrote a program in Excel VBA (yes, that is actually possible. Bizarre, and in no way the most efficient way to do things, but possible). It uses VBA userforms and scripting to completely hide any and all traces of excel, and uses a separate workbook, with all the data hidden of course, as a database. Granted, a remotely competent user could have created the same functionality in MS Access in a fraction of the time, but there it is.
On showing my first serious draft of this 'program' to my supervisor, she commented that it was ridiculous that I still worked there, because I'm way too smart for that job, even for what they're paying me.
When your boss tells you that you're under-employed, that's pretty much game-over.