I call the few business days between Christmas and New Year the "Holiday Hump", kind of like people call Wednesday the "Hump Day". We're in the midst of the holiday hump here. A long Christmas weekend is out of the way, but I still have the in-laws descending on my house this weekend, and whatever we end up doing on new year's eve.

I have neglected this blog, and I'm considering making it my new year's resolution. I'm still really into reading various blogs, even if the RSS feeds I subscribe to have changed over time. I still enjoy reading Joel Spolsky, Jeff Atwood, Leon Bambrick, K. Scott Allen, and others, but those are the first that came to mind.

I suppose I started this blog because I wanted to be able to contribute to the community like these other people have inspired me, but I've found that writing doesn't come as easily to me as I'd hoped. Also, I realized that blogging is life for some people and it's just a supplement for me. I still think I have things to contribute from time to time, but I also have been working on such mundane things lately that nothing has come up.

It will be really interesting to see what pops up once the current project I'm working on is up, and into the new year. This project is due the first week of January, but we'll see about that. I was complete with code, had the design documents updated, had started on a user guide and had my one resource doing unit testing and working on example configurations when I was blindsided on Friday morning. I should have seen it coming, but there has been totally new functionality added to the requirements. Requirements being a non-existent document. I'm not really upset about the change of scope because I've had to deal with it plenty of times in the past, but I'm not sure what will happen if I don't meet the deadline. Things are so disorganized here that I really have no idea.

Holiday hump, project hump (almost), and unsure about what the new year will bring. In the face of all of this uncertainty, I'm still blessed with a loving family and I still love what I do. Maybe I don't need any new year's resolutions after all.

Labels: misc

Last night was shaping up to be a pretty dull Halloween. My son wasn't feeling well (probably just teething) and with the rain and temperature dropping, we decided to not go out for trick or treat. At this age, he wasn't looking forward to it, so it's not like he even noticed.

Then, at 8pm, we heard two gunshots outside our house. They were 5 or 7 seconds apart. After the first one, I thought it might have been a backfire from the state route just on the other side of our neighbor's house. But the second gunshot convinced me of what they were. I tried calling the neighbor whose house was in the direction of the gunshot, but got no answer. His lights weren't on and we suspect that he might even be out of town. Our neighbor on the other side heard the gunshots too, and agreed that they were gunshots, not something else.

I called 911 and the police showed up about 8:17pm. The first officer parked in our driveway and approached our front door with his hand on his gun, still holstered. There was a second police cruiser on the road that stopped in front of our house. I opened the front door and told the officer what we heard, but stayed inside. The officer said that they'd go check out the neighbor's property, and he took off across my front lawn. The other officer stayed in his cruiser and drove over to in front of the neighbors house.

They searched the neighbor's property, the first officer on foot, and the second using the spotlight on his cruiser. About 5 or 6 minutes later the first officer came back to say that they didn't find anything. The neighbor's house was secure and they didn't find any bullet holes in the windows or walls of the house. The officer also verified that the cars parked in the neighbor's driveway were ones that I'd expect to be there. There was nothing else for them to do at that point and the officer told me not to hesitate calling 911 if anything else happened. The officers then hurried away. I got the impression that they were probably pretty busy on a Halloween night.

All in all, I think the police showed up fairly quickly and did a good job investigating the incident. I don't like not knowing what actually happened, but at this point I don't think I'll ever know. My wife thinks that it might have been someone just shooting out of their car as they drove by, but I don't think that was what happened because the shots were too far apart to be coming from a moving car and not sound differently. I still haven't gotten a call back from the neighbor whose house the shots sounded like they came from, but maybe that will provide more insight.

Labels: misc

My first goal on 43 Things was to create a blog, so here we are. I'm planning on using this blog to post topics about software development, but I may sneak in something personal every now and then. Now it's time to change that goal to something like "don't let your blog stagnate."

Labels: blog

I'm working on a new project where I laid out the class structure in ArgoUML and generated the C# code. This was my first time using ArgoUML and I found that I didn't like the generated code that much, and had a lot of changes to make. One such change was to refactor my public members into private members exposed by public properties. In Visual Studio 2005 this is no problem with the built in refactoring. This project, however, needs to use the 1.1 .NET framework, so I'm stuck using Visual Studio 2003. So I resorted to Find & Replace using Regular Expressions.

The regular expression used for the Find:

^{:b*}public {:a+} {:a+};

And the expression used for the Replace:

\1public \2 \3\n\1{\n\1\tget { return m_\3; }\n\1\tset { m_\3 = value; }\n\1}\n\1private \2 m_\3;

This results in code like this

public string Name;

being replaced with this

public string Name
{
   get { return m_Name; }
   set { m_Name = value; }
}
private string m_Name;

I suppose it would be a little better to somehow replace the capital first letter in the private member with a lower case equivalent, but it's not really that big of a deal ... at least, not big enough to spend more time on this task.

Edit: I need to come up with a better format for posting code.

Labels: programming, regex