Monday, January 01, 2007

Just a few goofballs hanging out on New Year's Day. We watched WWE, played the 20Q game, did party poppers, ate nachos, and whatever. And hey, goofball is fun.

Greg, Rogan and Cory
Above: Greg, Rogan and Cory hanging out at the place (listed in order seated in the picture, left to right and I explain that just so Cory doesn't get upset about being last, heh).

Add/Read: Comments [2]
Humor | Personal Stories | Random Stuff
Monday, January 01, 2007 7:34:49 PM (Pacific Standard Time, UTC-08:00)
#  

I'm in the process of moving my email for the greghughes.net domain to a new mail server, and I've realized - once again - just how complicated spammers have made our lives. Especially from a technical standpoint.

PTR records in DNS and RBL records on services that no one ever heard of and which have no set rules to determine what gets on the list or how to engage them in getting off a list. What a mess. Luckily I am not on any RBL lists (with the exception of one idiotic one that everyone seems to be on, and which I certainly hope no one ever uses). But I have friends and acquaintances who have been in that boat before and it's not fun.

But the biggest pain with moving a mail server has to be DNS propagation and the wrenches people throw into it. Enough time has passed that all locations should be pointing to the new mail server, because the old DNS records have expired. Yet there are a significant number of (large and prominent) email and Internet service providers (including my own) that are apparently caching longer than the record provides. Fun. That means I am checking two mail servers (and that's a bit of a challenge, let me tell you), and that I cannot send email to pretty much anyone until the planets align and the name server records line up.

Even my web site still has a few bots and spiders and other systems munging through it. I wonder if they'll notice when I turn it off?

One other thing I have observed. The spammers also don't respect caching of DNS records, but in the opposite manner. Instead of caching a record for too long, they completely ignore the cache settings to make sure they can flood your new mail server with as much crap as possible, as quickly as possible.

Ah, gotta love it!



Add/Read: Comments [0]
Tech | Things that Suck
Monday, January 01, 2007 10:47:54 AM (Pacific Standard Time, UTC-08:00)
#  
 Saturday, December 30, 2006

New RDP client UI MS has released v6 of it's Remote Desktop Connection client.

Remote Desktop Connection (Terminal Services Client 6.0) provides a way to use any new Terminal Services features introduced in Microsoft Windows Vista and Microsoft Windows Server Code Name “Longhorn” from a computer running Microsoft Windows XP with Service Pack 2 or Microsoft Windows Server 2003 with Service Pack 1.

The features in this release are really about Vista and Longhorn server for the most part. But, one feature that works in XP while connecting to Windows Server 2003 (and I was prompted to do this by default after upgrading, by the way) is the option to provide the username and password in the client before logging on, and the option to save that information so you don't have to re-enter it each time (not sure I like that specific idea for security purposes, but it has its place, and there are several security enhancements when connecting to Vista and Longhorn server).

Download it from Microsoft here. Read the KB article here (which includes links to versions for OSes other than 32-bit XP, as well).

(via Omar)



Add/Read: Comments [1]
IT Security | Tech
Saturday, December 30, 2006 2:14:42 PM (Pacific Standard Time, UTC-08:00)
#  
 Friday, December 29, 2006

To add to my totally analog Christmas (and the subsequent mostly-analog vacation week that's followed), my friend Cory and I started building a shed in the back yard this morning. We only had a few hours to work today, but we got a lot done. It was 32 degrees out but we hardly noticed. Below are some pics, which I will update periodically as we make progress. Click on each to see a larger view.

A few notes for anyone who is considering taking on a project like this one:

  • Having someone around who actually knows what they're doing is a great thing. My buddy Cory's done a lot of carpentry and construction work, so he's The Boss. Foreman. Teacher. All that stuff. Thank goodness.
  • Seriously, don't even think about picking all the stuff out yourself and trying to haul it home in your truck or car. For this project we went to Home Depot for the materials (due to some reasonable prices and a very attractive zero-payments/interest-for-a-year financing deal). We went to the pro desk, handed over the plans and the parts list, along with $59.00 for site delivery, which was done on a semi truck with a big forklift. This was definitely more than worth the cost. The pro desk helped tweak things, checked the plans and corrected a couple assumptions I'd made, and generally made it a better experience (so far, anyhow - heh).
  • Speaking of plans, shedplans.com is a great place to go and spend a small amount of money for a quality, detailed building plan. I spent $15 with them and it would have been worth it even if I didn't use the plans at all - The building information in there was great and worth the price alone. Of course, we are using their plans for our structure (which is a 12x16-foot gable-roof shed).

Day one: Floor framing

Cory pretty much leveled the site the day before with a shovel, a rake and the 4-wheeler. So today we put together the framed floor. It's in two sections, which were later "wrapped" with a second layer of treated 2x's:

The site is ready to go, and the floor sections are laid out in the general area:

On the piers, it starts to look more substantial - like you got something done. In the last picture Cory and Diogi survey the work we did.

More to come when it gets done. :)



Add/Read: Comments [4]
Random Stuff
Friday, December 29, 2006 11:52:32 PM (Pacific Standard Time, UTC-08:00)
#  

Joel Spolsky points to a blog entry by Dmitri Zimine that does a good job pointing out the problem with interruptions when a software developer or team needs to be heads-down on a project. The posts are more than a month old, but they're still just as relevant. As an agile development team manager, I know a significant part of my job is to provide a layer of abstraction between the dev staff and everything else in the world. Interruptions and distractions have a compounding, maybe even exponential delay effect on major software projects - a half-day interruption can result in several days of lost productivity (especially if the half day is scattered an hour or half-hour at a time over a couple days, for example).

I've often wrestled with trying to strike a balance between what needs to get done on some project and the rest of the needs (and wants) that are out there. Ultimately, here is what I have come up with:

  1. Bugs that impact real customers simply have to be fixed. Bugs happen, and so fixing happens. How important and impactful the bug is determines the priority of the effort and whether or not (and when) to interrupt the programmers.
  2. It's my job to put myself in the communication loop, as a filter. I have fallen down on the job a bit in that regard recently, partly because of my work travel schedule. I need to re-insert myself to enable the development staff do their jobs even better.
  3. It seems obvious but it's worth saying: You cannot make everyone happy all the time, and you should never try to do so. All you'll get is disappointment, and that's not a worthy goal.
  4. Nothing is ever as big a deal as it seems. Everyone has their own priorities, and it's human nature for people to make their own priorities seem highest. But that's not the way it really works. See Number 2, above, for a solution.
  5. Focused developer and QA people are happy. Distracted ones are grumpy, much less productive and complain a lot. In other words, there is a domino effect. Professionals expect their managers to help them do their jobs well, and that's a reasonable expectation. My job is to hire good people, make sure they have what they need, and then let them do what they do best.

I truly enjoy working with my team in an agile world. It's always a fight to strike that perfect balance, and since true perfection is impossible, it's always a moving target. But a good manager will stay on top of that target, anticipate problems, adjust to the environment, and head those pesky issues off at the pass whenever possible.

For the record, I'm about as far from an optimal agile dev team manager as one could find. I am learning something new every day, much of it OTJ style, and there are other people where I work that are quite literally pros in the agile management field. For all I know, they may have something to say that contradicts what I've espoused. Should be interesting.



Add/Read: Comments [2]
Tech
Friday, December 29, 2006 10:44:11 PM (Pacific Standard Time, UTC-08:00)
#  
 Wednesday, December 27, 2006

I just realized something interesting. This year I had a completely non-techie Christmas. Of the gifts I received, only one was even remotely computer related (but hey, no need to go cold-turkey, right?). I think that's kind of cool. Plus this Christmas was a good one once again, spent at home with friends.

My friend Cory (who appears to have started blogging for Christmas, heh) points out that the act of giving is a good one to practice. I agree.

Of course, receiving is quite fun as well, and I received some very thoughtful gifts this year. Perhaps my favorite (it's hard to choose you know) is a painting that Cory made for me to hang in my office. It's based on a painting by Peter Pongratz from Austria - we saw a bunch of his (rather interesting and crazy) art at the Belvedere museum in Vienna a couple months ago in a display called Sweet Home Vienna. Cory took the Pongratz-style phrases in the painting and replaced them with Office Space lines. Heh. Pongratz and Office Space are a lot alike.

An analog Christmas. Nice.



Add/Read: Comments [1]
Personal Stories | Random Stuff
Wednesday, December 27, 2006 2:02:17 PM (Pacific Standard Time, UTC-08:00)
#