Oh, such a happy day, but super busy for me... I've been putting up with the old MeetingMaker for two years now, but today we're launching the latest version of MeetingMaker. Wish us luck! It's not a revolutionary difference, but it looks a lot nicer, and it has the following new features that I really really like....

Sorry for the gap in posts, I'm out of the office right now, back tomorrow. However, I was reading this interesting article in the New York Times and I wanted to post it.

We've all done it, browsing the internet while you're at work. Some of us have done it a little, some of us have done it a LOT. I'm probably in the middle... the worst for me is that a lot of the things I do at my desk require waiting at times for longer than I'm patient enough to wait. It's far easier to read a quick article somewhere than try to work on two or three projects at once. (I know this sounds dumb, but in programmer terms, think of trying to write three essays, one in French, one in German, and one in Mandarin... It's tough to switch gears.)

Do your backup. I don't care how.

I learned this project organization method from my boss, and it appeals to my obsessive compulsive nature....

Well, I made it to the beginning of the semester, still somewhat regularly posting. A lot of you quit commenting, and it's probably because life has gotten less sane with the kids coming back, and that's understandable. (Also, I think I've gone off on some tangents lately that maybe didn't qualify for a comment...)

The blog also made the "big time" and got an official link off of Computing Services' website, and I've noticed a couple of folks who weren't in class following the blog. Awesome.

So, class dismissed. (This was, after all, in theory a class...) However, I'm going to keep blogging. If anyone has something they want me to talk about, either comment somewhere, or email or call me directly and I'll either research it for you, or steal liberally from your idea, which ever you prefer! I enjoy thinking about organization, but I think I'm a poor authority on it and would rather learn from you and then share what I've learned with the world.

So, it's time to down another Faygo Rock & Rye and get back to working, hopefully in a more organized fashion than when I started this blog.

It's a new academic year and the kids are back. I always love this time of year because I don't work directly with the kids, so my work load is roughly the same, but everyone seems so much more urgent and energetic around me and it rubs off... It's a good time to make a "new academic year's resolution", and here is mine.

We have a shared folder our department uses to keep track of stuff, but it's grown by leaps and bounds and there are a ton of things in there. I've had cause to look for a couple of things recently and found I couldn't tell where things were, then once I found them, I wasn't sure if what I had found was accurate documentation. What should we do?

So I promised to explain the holy grail of a clean backup, especially in the context of the last post regarding massively changing the location of all of your documents. Stick with me on this one, since it's conceptual, but hopefully will help you understand the intricate gears of our backup plan for users.

Thanks for visiting, if you've popped over because of the link from the help desk! Feel free to peruse the past articles, comment, and if you want to know more about a topic, let me know.

I had to post this though, because I've tried hard to average TWO posts a week (rather than the advertised "one post" on the help desk), and for the most part, I've done it. I guess that's what I get for free advertising...

I do try to schedule posts to hit Tuesday and Thursday mornings, but if you do want to add my little old blog to your reading cycle, I really recommend an RSS reader, like Google Reader.