Father, Husband, Employee, Coach, Tutor I had been pondering a post on how impossibly busy I have been lately. You know, the 45-60 hours in the office, the 2 hours on the road back and forth, coaching a bunch of 6-7-8 year olds and tutoring someone in database concepts. And blogging of course.

It doesn't seem to have quite the punch now.

Here's what it would have looked like anyway...

Father
With all that has happened in the last couple of years, I still get to come home to people that like me no matter what. LC and his battle stories with the girls at school and Kate...well, she just is. Her smile lights up the room. The infectious laugh...the hugging (finally!)...she just makes my day.

Husband
Intentionally left blank.

Employee
Move along...nothing to see here.

Tutor
It's been about 4 weeks since I began tutoring. I thought I would post more on it, but I've been so busy with everything else that I just never go to it. That should change now though, at least for awhile.

There is nothing like having to communicate complex systems to those who don't know the first thing about databases. Where do you start?

Last week was especially difficult. We had to diagram some tables based on one paragraph of requirements. This was more inline with logical modeling as well, which I don't have a lot of experience with. Which means, you have to represent (as I understood it anyway) your relationships without use of an intersection table. WTF?

Coach
One of the best things in the world. If you ever have the opportunity to coach young children, take it! Yes, it's painful at times. Yes, it is like herding cats. Yes, they do not listen. <-- does that even make sense?

But...you can yell at them for an hour straight. I don't mean the jerk kind of yelling, I mean the fun, obnoxious kind of yelling. Whatever that is.

For whatever reason, I'm naturally loud. Amazingly, I get louder on the baseball field.

There is no better way to turn your day around than by yelling at a bunch of kids. The best stress-reliever of all time possibly.

Labels: family, life, work

  ¶ 10/20/2009 11:12:00 PM   3 Comments Links to this post

  Learning From Failure I think I began reading The Daily WTF about 4 years ago. I don't miss or skip a post.

I remember this one time, probably about the time I began reading the site, I had to automate a process to move files from one server to another. Originally, I had tried to create a network drive (yes, it was Windows) on the database server so that I could just use a simple Java class to read the directory and then load the files via DBMS_LOB.

I had ultimately decided on a service, but I didn't know how to write one for Windows. Then I found the Java Service Wrapper which would allow me to write the guts in Java and then install it on Windows as a service. Perfect.

Now that I had that settled, I had to figure out how to detect when a file was read to be moved. I decided on a looping mechanism, to check every minute or so, to see if a file was available. It looked something like this (I'm a tad rusty, so bear with me):

package project1;

import java.util.Date;

public class Class1
{
  public static void main(String[] args)
  {
    Class1 class1 = new Class1();
    Date d = new Date();
    long l = d.getTime() + 1000000000;
    String s = String.valueOf( l );
    
    for ( int i = 0; i < l; i++ )
    {
      //some sort of MOD "wait" here, then check for the file
    }
  }
}

It wasn't pretty, but it seemed to work.

Then I got a call from the server admin.

SA: "You've got something running on this machine that's spiking the CPU."

Me: "Really? I can't think of anything."

SA: "Well, take a look and see if you can find anything."

Me: "10-4"

Sure enough, go into Task Manager and there's java.exe hogging up all the CPU. WTF?

I just ran this on my machine and you can see the CPU start to spike:


Off to Google to see what I can find. During my research, I found mention of a small method called Thread.sleep(long). So I replaced my brilliant add 1000000 to the current date with Thread.sleep(6000), or whatever equals 60 seconds. Problem solved.

A short time later I read a post on The Daily WTF about the same exact problem (I can't find the exact post for the life of me). The "victim" did the exact same thing I did. The solution was the Thread.sleep() call.

Me = FAIL

One more short example.

Over beers, a friend (see last entry) of mine and I were discussing the failure of the North Korean missile launch. I said, "Idiots." He said, "They're going to learn a lot more from that failure than they would have had it suceeded."

Spoken like a true engineer I guess.

The point? You learn by trying. You learn my doing. You learn by failing. Whether you realize it or not, you learn. (Well, some people don't, but that's another post). If you're reading here though, that probably means you have a passion for what you do. That means that you are trying. You are learning (maybe not here specifically ;).

Here's to trying and failing and hopefully trying and succeeding.

Labels: development, failed, ideas, life, work

  ¶ 7/02/2009 12:21:00 AM   0 Comments Links to this post

  What a Life... Saturday afternoon I had scheduled to go golfing (I'm not a regular golfer) for a friend's bachelor party (believe it or not, no strippers). Saturday morning wifey was sick so I decided to cancel the day of golfing (drinking). For weeks I had also planned on attending the Museum of Science and Industry (MOSI) Tweetup Saturday night. Since wife was sick and there was a second event, dinner, I opted to go see my friend and celebrate with him.

My friend is a former teammate from UF (Go Gators!). Of the 8 people who attended, I was the only one not a high school (or further back) chum.

Anyway, one of his high school friends (and teammate) was a guy who played 12 years in the Big Leagues (MLB). He retired 2 years ago.

Me:
"So, what do you do now?"

Him:
"I chase my kids."

Me:
"Wow"

35 years old and his job is to chase his kids. How sweet is that? He never has to work a day for the rest of his life. I wonder if I had been fortunate (read: talented) enough to play MLB if I could handle doing "nothing" for the rest of my life? I couldn't imagine it now...I work almost non-stop. Either for work or just learning something new. Doing "nothing" would probably drive me nuts.

What about you? Could you retire at 35 or whatever your current age and do nothing?

Labels: life, work

  ¶ 1/18/2009 10:39:00 PM   6 Comments Links to this post