No new pictures this week, as very little has changed. The last set of pictures revealed a couple of problems. The downstairs sink is supposed to be white (or Coco Blanco as the technical term). Also, the master shower is supposed to be semi-frameless. So, last week, those were noted to the construction office. I think the new sink is in a box, but the shower replacement is nowhere to be found.
Things are starting to get interesting. The final walk through date is May 4th. The closing is on May 11th. I can’t believe that the house will be finished in little more than 3 weeks…
As you saw in my previous post, my new company is hiring developers. Well, we found one so far. Amazingly, that developer has a similar background to me and my boss. Hopefully that will make for a easier fit.
But, that’s not the point of this entry.
In creating an interview process, my boss and I had a couple of discussions about how to approach it. We’ve both had people who interviewed great but they fell apart when they actually started developing. I had read a blog entry about someone who’s company actually gave the candidate a very simple problem, a computer with a development environment, a time limit, and let them write a program to solve the problem. I *LOVED* that idea. One interview I had gone on about a year ago did a similar thing, but they went pretty elaborate where one had to set up a web page, do the database connection, and do a bit with several parts of the framework. I personally didn’t want to have to set up that environment for someone, so I convinced my boss to do the simpler problem. He agreed, so I wrote something up.
Now, in writing up the problem, I wanted to present one little twist. I put an impossible condition into problem. Why? Because I wanted to see how the candidate would react. In fact, I think the company I did MY interview for did the same thing. They had a faulty database setup. What I threw out was simpler. But, it was a flaw in the requirements, not something that would stop someone from coding.
I learned something interesting with this test. My expectation was that the candidate would see the issue and ASK A QUESTION! That is my #1 pet peeve. If one does not understand something, they need to ask questions. I’ve never been upset with someone who honestly doesn’t understand something. I *DO* get upset when people don’t at least TRY to figure things out. It is a very fine line to walk. There is a point where one must be able to discover answers for themselves. BUT, in our business world, clarification is important, as what the customer asks for is not always what they say. It’s far too easy to get into the ‘only do the requirements’ mentality that most big company development seems to have. When things don’t make sense, it’s best to stop and try to make them make sense, else you’re wasting time.
Speaking of wasting time, it seems that’s what I’m doing. Time to crash. More stuff later!
It’s not that things have been slow, but too much has been happening, and little of it relevant. Some things I just don’t wish to talk about have been going on, and until they are resolved, I’m keeping my mouth shut.
First, on the tech front, I finally got a new motherboard to replace the one that died a couple of weeks ago. The replacement is now running, I moved Vista back (still no major problems with moving it!), and all is right with the world of my computer. Next, I was able to rebuild a ‘jinxed’ computer for one of my clients. This thing was no end of trouble, with the final straw being that the motherboard would not recognize the keyboard. So, I replaced the motherboard and case, and that seems to be running very well. Another success story for Vista, as I had installed Vista on the computer earlier, and it survived changing the motherboard out with no adverse affects.
Second, I have had a LOT of client work lately, which is one other thing that has kept me from blogging. 9 or 10 hours a day at work, then another 1 to 3 hours a night tech-ing will really catch up to one quickly. At least the client work has been interesting, to say the least. Try fixing a dead CD-ROM drive on an 7 year old laptop (32 megs of SYSTEM memory!) by installing an external drive. They supplied the drivers on a CD… Uh… Doh! Unfortunately, that was not a successful repair. Most everything else, though, has been going well.
Third, the house. I haven’t been able to get by to take pictures, which is why no recent updates. There is a lot of stuff that is happening, I have a final walk through date and a closing date, which are rapidly coming up. As they get closer, I’ll let those details be know.
Finally, I have a couple of little rants about blogs and developers. I saw one of the Microsoft guys blogging about finding a house, but he was real apologetic that the post wasn’t about code! Now, the code blogs are fine, but geez, you’ve got to live! If I only blogged about code, this would be the most boring, least read blog out there. (Not that I have many readers anyway!) One thing that I think us developers loose sight of is the ‘Big Picture’. Ultimately, we write software to enhances people’s lives. The best software makes impossible tasks easy, and difficult tasks simple. When we take a simple task and make it incredibly difficult is when software is not being developed well. Why do you think people like Macs? They are simplier. They are designed so that people ‘get it’ very quickly. Not so on the PC. Most of the concepts are foreign to people, and they never will get them. Ok, I’ve wandered a bit here… back to my point. What I’ve been trying to say is that living life helps make one a better programmer. Someone who can spit out code, but never understand what the ultimate goal is, is just wasting time. So instead of ‘Live to code’, do ‘Code to Live’. And, heck, maybe the writing about one’s impressions of life will be more meaningful than what the latest interesting C# operator is.
Ok, enough is enough, time for me to crash. I should have more blog updates this week, as time permits.