Day In The Life of Baz

Had my second interview with the guys down in Plano today. I’m not really sure how it went. First of all there was the time issue. I was sort of behind schedule leaving Wichita Falls due to some issues with the rental car I had. It basically stunk of smoke, so I had to return it for another one. After that was taken care of I flew home, got dressed and zoomed down there. Almost got lost a couple times, but nothing real serious.

But this is the interesting part right here. When I was five minutes away, I needed to use the restroom. I decided that it would be best if I don’t walk in there and the first thing out of my mouth is: “where’s your bathroom?”. So I stopped a couple minutes early at a gas station. Here’s the funny thing, my zipper broke right then and there. I guess that’s why you need a portfolio at at interview: to hide the fact that your fly is constantly open and can’t close.

Anyways, I had the interview with a Vice President of Development. Nice guy actually. We spoke about ambitions and what I want to do and stuff like that. Just the normal interview stuff.

Maybe getting a job to do a “database” for the Counseling center at Midwestern State University. Currently they have a database “written” in MS Access. All the forms etc. are contained the the Access database and it is accessed (lol) over the network in the office.

My rebuild would be done in C# of course, since that’s what I’m learning right now. I haven’t really decided yet, but I think I’ll just stick with the MS Access database format right now. A SQL Sever 2005 setup would be best, but I don’t think the have the resources available for that (i.e. A dedicated machine to run the server). So I’ll just plop the Database file onto a computer somewhere on the network and let everybody have fun that way.

I’ve done some preliminary tests with the whole thing and it looks promising. It was done over my home network though, and I still can’t get that to work right. The only problem I’ve come across is what happens when two people try to save the same record. The first person gets to save, but the second person is greeted with an error that crashes the program. It will be simple enough to do a quick exception handler to solve that problem and besides that’s the way it should work. I may go a little bit deeper into “locking” a record when it’s being accessed, but I’m not sure.