Well I had a good game of underwater hockey tonight. I only got elbowed in the face once, my ankle skinned once and my elbow whacked against the pool bottom twice. Oh and I got my stick hand hit pretty hard. But the real gem was the turn out of good players. So each time I received the puck I was too busy fending off tackles, instead of making good ground. Scored a few goals, got some good passes in and generally had a good time.
A hybrid post where I plan to wonder through different idea spaces (compared to going off on tangents while trying to keep to a single idea).
Anyway there seems to be more support in .Net 2.0 for smart clients with things like ClickOnce for deployment management etc. It just seems strange to me that anyone would do anything different. When the application has a known/controlled install base, anything other than smart/thin client based development seems like proposing a substandard experience.
The other related thing is I had an interview at the local HP office yesterday. The building looked really nice, they had plenty of parking and quite a nice view, but no pool. The ~3+ hour interview was fun. I had to implement a piece of software that was meant to be a web form (ASP.Net) but I have no experience doing web forms so they changed it to win form. The task was to build a simple customer management app. But I had two hours to get through as much of the feature list. Gosh writing a slap dash app is so against the ideas of clean application development. After patterns like MVC, frameworks for smart clients and unit testing, been asked to slap it together actually seems like the most worthless of tests. The only value I can see from the test is how much domain knowledge the interviewee has. Things like clean abstraction, commenting, unified event handling, get thrown out the window. It was more stressful than the algorithm programming on TopCoder. I think asking me to talking them through a design of what I would have done would have added more value. It would show I knew how I’d tackle the task and the fundamentals of client UI design. This would appear to be of more value than weather or not I could slap together code that followed none of those principles in a tight time frame. Especially when afterwards we discussed how so little time is spent coding, and the projects are well managed through a structured development cycle.
David and Juval at the beginning of the audio interview where discussing about how this is how software should be engineered. I agree with this. Big systems need big process. My problem is I’m not the biggest fan of big process. I’m a fan boy of prototyping stuff. Solving the “but you can’t do it” type thing. The skunk work projects. Working thought task lists that are planned out a year ahead is not me.
The Coding Challenge is On!
I entered the Google Code Jam yesterday. I was pleased with my effort when after 50 minutes (of allocated 60) I had completed to two assigned problems. I was working on problem set #1 (room 7). I had a score or 502.75 point (out of 1000) and at 13 hours into the 24 hours period, I was ranked 46th for my problem set.
But my 750 point problem failed system testing, so my final score was 178.59, this put me in 266th (of 939 people, but 482= was the last place) position for the problem set. But my Google rank was 1359 which is better than my best Top Coder ranking.
Which reminds me that the night before I entered the Top Coder SRM 259, I was in division II after my poor Top Coder Open results. The three problems where easy to-do so I’m now back in division I (but only by 2 points), so I need to pull finger and do better in the next SRM. I got top score in the room I was in (#16) and I placed 11th (out of 273) for the division. So even though it was 11pm when I started and 1:30am when I went to bed, I was feeling good.
I went to a .Net User Group meeting last night. It was hosted at SunGard and Adam Cogan was the presenter. He gave a good talk about the features of SQL Reporting Services 2005, with a few side stories while the designer was busy “designing”. The Design tools were very slow at times, but he was running a beta version under virtual PC, so there is room for forgiveness. That mixed with I not sure how much work was been done behind the scenes.
But really what impressed me was how simple it was to click and drop it all together. I really like the Client report building, that feature would come in handy here at work.
All’n’all I really useful piece of software. For new development Business Objects must be packing them selves.
One of the good titbits was Adam explaining how he deploys database applications, and how he thinks it’s the application responsibility to set-up the server correctly. He showed how they laid the files out, and how the application did the checking and loading of .sql and .rpt files.
But the highlight of the evening was wining a free MSDN Polo Shirt.