If you’re going to work good, you need to eat good.

Just to quell any concerns that I may be blowing my diet to pull an all-nighter tonight (and yes, I do expect to be here all night), I thought I’d give a glimpse of what the menu will be like for the next 20-23 hours:

For starters, we’ve got some boneless skinless chicken breast.  That alone is good stuff.  I’ve also got some sweet onion, broccoli, zucchini, and mushrooms to throw into the mix for what stands to be a kickin’ stir fry combo, sans the rice.  You’ll also notice some eggs and OJ there as well.  That’s for breakfast.  Yes.  Breakfast.

I’m a geek, but I love to cook, and I can be quite serious about it.  I might have also brought my wok and some olive oil with me to assist with the stir fry.

It’s going to be a good night.

I’ve been in somewhat of a blogging drought lately.  Honestly, I’ve been trying to think of stuff to write on but those ideas have escaped me.  However, my mind has been far from blank … just some random miscellany

-> I am psyched about Sharepoint training in January (read more about it here).

-> I snagged a couple helpful apps for my Q last week:

Power Tasks - An uber-enhanced version of the Task List in Windows Mobile, this software reformats your task list into something similar to the “To-Do List” view in Outlook.  Very handy for me, because I’m keeping more and more of my assignments here.

Gentimer - A sweet clock/timer/stopwatch application that I’ve started using to keep track of ticket and task times.

-> The domain rebuild that I’ve been working on is going well.  I’ve been taking some time to document every non-default configuration that’s happening on the new domain controller and exchange server.

-> I’ve been using our helpdesk application to track my time spent in video versus IT.  I’ve been pretty surprised by the results.  (On the subject of ServiceDesk … I wish they would release an upgrade patch from version 6 to 7.)

-> We’re going to be installing Leopard on our Final Cut rig this week or next.  I’ll be interested to see if the new Automator can add some automatic sweetness to our recording/encoding on Sunday mornings.

That’s about it for now… hopefully I can think of something to post on soon.  If nothing else, then you’ll hear more about the domain rebuild as the time to switch over draws near.

Sorry for suddenly going silent since Wednesday morning.  There has been a LOT going on since then.  I’m just going to take a few moments and recap the week.

The IT Roundtable at Granger was awesome.  I had a chance to sit and soak in some dialog from individuals that I consider to be much sharper than myself.  I’ll post more later about some stuff that I took away from the ITR.  Mega-props to the Granger IT guys for making this happen!

Thursday was a myriad of meetings, phone calls to make, and orders to place.  We’re gearing up for budget season again, so I’ve been working on next year’s goals and what it’s going to take to accomplish them.

On Friday I spent most of the day tinkering with a Miranda DVI-Ramp2 as we demo it for this weekend.  I’m pretty pleased with what it’s capable of.  After that, it was off to the Swiss Festival in quiet little Sugarcreek, Ohio for some walking around, running into people we know, and just basically enjoying the fall weather.  The best part of the festival?  Fried cheese.  No lie, man….best stuff ever. (4 out of 5 physicians disagree).

Well, unfortunately it looks like we won’t be doing any live streaming.  However, the audio from the Roundtable will be recorded and will be available in one-hour chunks at a location to be determined.

This morning I walked into the NewPointe offices after 2 weeks of being on vacation.  Don’t get me wrong, I would still rather fish, but it felt great to be back to work, also.  To add to that, the domain controllers that I was having problems with yesterday seem to be holding time just fine.  There were a few tickets that piled up over 2 weeks, but that’s about it.  All-in-all, it was a great first day back from vacation (or “holiday,” if you’re reading from across the Atlantic).

I’m headed to bed here in a few minutes, and then I’ll be driving out to GCC bright and early tomorrow for the 2007 Church IT Roundtable.  Nothing like coming back from vacation and going straight into a road trip.

I don’t know if I like having the weight of my iPod (plus the case) resting on its connector, but to each his own.  This method definitely wins the “budget prize.”

Check out the article here.

I’ve been shying away from social networking sites for awhile now, just because it has always seemed like a chore to keep it all updated.  After some consideration though, I decided to open up an account on Facebook.  It’s actually been there for awhile now, I just decided to update it today while I’m waiting on other stuff.

Check out my profile here and add me as a friend if you’re so inclined.  You know it’s the right thing to do.

…And I don’t mean ”decorative good-looking”….pretty stenciling on the server rack and trim on the IDFs that match the woodwork or carpet.  That’s unrealistic and quite frankly, a little fruity.

I’m talking about “functional neatness,” if you will.  Wires tied down on racks, color-coded cables to show what is being linked up, proper labeling on every wire and piece of equipment, that sorta thing.

Back in the day I was terrible about this.  I would just fling wires around and plug in what needed to be plugged in and as long as the little green lights were blinking on the switch, I didn’t give a rip what it looked like.  These days though, this is something I take pretty seriously.  Whenever we hook up a new piece of gear or patch in a new workstation, we make sure that things aren’t only functional, they look as good as they can.  So for me, can IT be too “good-looking?”  Definitely not.  Here’s why:

If it’s hard to look at, it’s going to be hard to work on.  This is especially true in the IT world.  If you need to trace down a link, do you want to have to look through a rat’s nest of CAT/serial/power cables to do it?  Of course not.  A small time investment on the front end can save all kinds of diagnosis time down the road.   Note: This also applies to sound systems.  Our sound guys do an AWESOME job of keeping our wiring tidy during upgrades.

Things need to be functional without you.  “Yeah, well I KNOW where every wire goes!”  Yeah, so?  You might get hit by a 1980 AMC Eagle tomorrow morning, too.  Especially in the church world, you need to make sure that the work can carry on WITHOUT you being there.  Don’t pass your wire mess onto someone else just because you know where everything plugs into! (This is also a strong case for…*cough*….thorough documentation.)

Here’s a couple examples of functional neatness. (here and here).  Now I’m not there yet, but this is what I want our patch panels at NewPointe to end up looking like, along with color-coded cables for each connection, whether it be printer, server, LAG, whatever.  Is this something that’s going to happen immediately?  No, not likely.  Next year?  The chances are good.  Nonetheless, it’s been something that’s been on my mind lately.

No, I haven’t been on vacation, things have just been that crazy these past couple weeks.  I’ve had to put my brain in different “modes” so much that when I came on Monday, I actually had to work at getting back into IT again.  I’ll some of what I’ve been doing over the next couple of days.

The first order of business today?  CLEAN MY DESK.  It’s turned into quite a mountain of paper and small parts over the past 2 weeks.  Time to make things pretty again.

I came in this morning to find a very interesting email waiting for me:

“Dude, what happened to your blog?!”

So I cruised over to davemast.net to check it out (I use Windows Live Writer almost exclusively now, so I hardly ever actually visit the site), and that’s when I saw this:

Well golly, I didn’t realize my site generated so much traffic.  Actually though… it doesn’t.

I called bluehost tech support to see what the trouble was, and when we looked at the log file, it was completely emtpy.  VERY interesting.

In any case, the site is back online, and I’m able to post again.  I apologize for any inconvenience this has caused anyone.