I just found a cool new site where you can map where you've been, and since I have a pretty impressive track record within the US, I thought I'd show you. If anyone knows anyone in North Dakota, I'd love to have an excuse to get out there. The rest somehow seem manageable on my own.
visited states for you
Less Impressively, my country count (7):
visited countries for you
Saturday, May 20, 2006
O the Places I've been!
Thursday, May 18, 2006
Great Plains?
This particular scene is from a cattle round up that we accidentally delayed--being the city slickers with cameras that we are. Needless to say, Amy was embarassed.
Family
There are tons of pictures from me and my dad if you want to take a look.
Sunday, May 07, 2006
Dance with the Rock
We also took a couple of lovely walks through the Mohonk Preserve and the adjecent state park. There were some crazy web-like nests which we discovered were some sort of cocoon for caterpillars. In this one, the big caterpillars were coming out and trying to find a way out of the tree. These guys were taking the scenic route and we caught them on film.... um, RAM?
Friday, May 05, 2006
Wake Up Call
This morning I woke up to about 14oz. of cold water spilled directly onto my flesh. Too bad it was only about 2am.
I managed to fall asleep with an open bottle of refrigerated water in my hand.
Nothing quite like wetting the bed at 24.
Wednesday, May 03, 2006
How to Talk to a Programmer
In my world, I spend a lot of time translating between normal human speak and programmer speak. And by programmer speak, I don't necessarily mean C# or visual basic. I mean programmer speak: the language used by programmers to communicate project goals, time lines, possibilities, solutions, etc. You don't have to know all the codes for colors in HTML, and you certainly don't have to know what HAL's favorite color was. You do however have to keep the following in mind:
1. Pretend like you think they are smarter than you. They think they are, so you might as well appease if you want the job done.
2. Be as specific as possible. They can smell a far fetched idea 18.2 miles away.
3. They think your "big ideas" are bogus. Remember that. Be discrete.
4. They probably are pretty bright in more ways than knowing how to concatenate two fields, so don't act like they're robots either.
5. If you want to "put pressure" on them to finish something, don't copy them on the email where you told your co-worker you were going to do it. (Ok, this goes for just about anyone).
6. Be realistic but firm about deadlines. Too quick and you'll get hostile response. Too lackadaisical and it will never get done.
7. It helps to have some basic knowledge of the soft/hardware you are working in to make this communication smoother. Consider taking a course in the "back end" of whatever it is you're working on.
8. Use sentences.
9. Hire me.
The funny thing is, I hate hate hate the phrase How-to. It is colloquial and stupid sounding. Use "process document" or "instructions" or "manual" or "guide" ... but How-To? It's like some awful bastardization of German syntax. Please.