I love seeing new things; innovations in existing markets.

In other words, things that make you say “Wow”, and compel you to tell your friends about your experience.

This is exactly what Hollywood Boulevard is doing for the movie going experience.

Forget the fact that the place is decorated really cool.  That’s a nicety, but nothing to write home about.

The innovation comes in the theater experience.  Forget cramped seating, this place has individual executive leather chairs that recline.  There is a table that runs in front of each seat so you can sit your drinks on it, AND they have a full restaurant and staff that takes food / drink orders during the movie.

We had chicken fingers and fries with a diet coke for 12 bucks.

And the movie prices are cheap too: $8 for an adult ticket.

Click here for more images of the place.

I will be going back for sure.

Dare Obasanjo has a post on the “Three Things I Learned About Software in College,” to which Scott Hanselman followed up with Three Things I Learned About Software WHILE NOT in College.

So here are my 3 from each category:

Learned in college:

1) A lot of people getting a CS degree will never be able to write a real program (as I was getting my degree in structural engineering (CE)).

2) New features and scope creep can cause projects to be never ending, and end up not being released at all.

3) How to really work hard, really study hard, and really focus on a task with a fast approaching deadline.

Learned OUT of college:

1) Just because someone has “Sr.” in their title doesn’t MEAN they know anything, but they might.  If their logic sounds flawed, don’t assume it is because they are “Sr” and you are “Entry”: you are probably right.

2) “Expert” can mean different things to different people.  You can be in the top 2% of one company, but a middle of the pack guy in another.  Avoid calling yourself an “expert” (or acting like one) unless you know who you are talking to, and you actually are the expert.

3) There is no “Best” way to do most things.  I had thought that if I looked hard enough and studied enough examples, I would know the “best” way to do things when I arrived at them.  But one groups “best practice” is something another group will not touch.  See the current OR/M arguments for a perfect example, or if you prefer just look at divide over using Datasets. 

That being said, there are definitely some agreed upon “Worst Practices”, so avoid these at all costs.

I saw a link from Scott Hanselman’s site to DreamInCode.net, which is looks like a community site for programmers.

I have been looking for a forum for software consultants like myself, so I will have to check out the forums:

http://www.dreamincode.net/forums/

There is the “Caffeine Lounge”, which sounds like the perfect place for me.  When the guys at starbucks start your order before you say anything, you have probably been in there too often.

Scott Hanselman has released the final .net 1.1 version of DasBlog, to be quickly followed by the first .net 2.0 version (thank god)!

I will have to upgrade things here when that happens.

I had one of my clients call me today with this message showing up on their production server after the power went out (big storm in the area):

17xx-Controller in lock up State

The server is old, and so I started to think worst case scenarios:  the controller probably died, the data is probably lost, backups probably don’t have everything, we are going to need a temp server, we are going to need a new production server etc.

Thankfully, this did not come to fruition, so if you get this error message on your Proliant, there may be some hope.

Go into the setup menu for the raid controller and you should be able to clear out the lock state simply by saving the settings.

Of course if your controller really did die, then this won’t help you.