Note to self:

To get the details of svchost.exe, which frequently gets a very large footprint and shows nothing in taskmgr other than used memory, execute the following from commandline:

tasklist /svc

Still don't know how to get details on the details...

Inheritance is a good thing.  It offers a great way to simplify coding through rollup of repetitive tasks and common attributes.  It is one reason why OOP is superior to most other programming methods.  It's a beautiful thing.

It also offers great job security.  Nothing endears your successor more than trying to figure out properties that are inherited 5 levels up in the abstraction with NO commenting or clue where to look.  And don't even get me started on N-Tier programming when N > 5!  Solutions get a bit unwieldy with 8+ projects attached.

This morning, a coworker told our BA that she needed to help the user to see the light.  From the look on her face, I think she'd prefer to help the user move toward the light.

This is the first book in a trilogy about the colonization of Mars.  The first book itself is enormous in scope, from the departure from Earth, the landing, building of settlements, commercialization, and finally Revolution.  Perhaps too large in scope.  The whole series was recommended to me by GP, whose judgment I respect.

Red Mars is the story of a handful of the "First Hundred" colonists on Mars.  They are the pioneers of the new frontier, braving the journey out, surviving planet-side and establishing the first settlement for permanent habitation.  We are treated to Love Triangles, political maneuvering, interpersonal conflict, and clique groups.  Surely some of my favorite themes.  And once the de facto leader of the First Hundred is murdered, we get political intrigue added too.  No investigation, just intrigue.

Technically, this was a brilliant work.  Narratively, not so much.  I found that I really didn't care about the characters and frequently lost track of what was going on.  I don't think it was that there were too many characters, because Red Storm Rising had more and was an incredible story.  Many times I would be reading a segment and have completely forgotten why they were doing some action.  It may be that as a dad of two very small ones, it was natural to fall asleep reading this book every night:  It was definitely a long read;  I purchased this book in July and only finished it this weekend.  My personal opinion is that this would have made a great prequel to an established series; the author tried to put way too much into this book causing it to be flat.  I am disappointed in this book, and despite owning the other two books, I am not sure I will read them. 

When you are looking at someone else's code, at what point can you definitively know it is bad code?  I'm sure everyone has their metrics.  Here's mine and so simple too:

Server Timeouts

Yep, real simple.  Here's the thing:  Nothing else, in my mind, shows a greater lack of understanding of the basic architecture of a system than poorly set timeouts.  For instance.  while not a bad idea to adjust the timeout of the SQL connection to fit what you are doing, setting it to 1200 means you don't realize that it means seconds and you just told your application to wait 20 minutes before doing any damage control.  I don't know about you, but ANY application that makes me wait 20 minutes for anything (without showing me real progress) is broken; I am impatient after 20 seconds!  Another example:  setting an ASP.NET app to use a session timeout of 300 minutes means you don't care about your server at all.  Why not store user specific information (full DATASETS!) in memory for 5 hours after the user has left the page.  5 hours!

These are real examples of code I am working on today.  I don't care how elegant your architecture is, Server Timeout abuse has always been a very simple indicator of developer incompetance.  Oh, and it seems to be in direct proportion of scale too.  I have actually seen an ASP session set to 3000000.  Yes 3 MILLION minutes.  That is 50,000 hours.  5 years, 8 months, 14 days, 13+ hours.  Yeah, that'll work.  I was not well loved because I wouldn't allow crap like that to run on my servers.

BTW, 3M minutes was by the same coder who thought LastName is a good primary key on a DB.  And when that didn't work, how about a composite key on LastName, FirstName.  Yep, World Class programmer.

Congrats to GP for his new change of status.  Sorry I missed the party, I bet it was memorable.

It took nearly two months, but I finally posted the review of the Foundation Series today.  The post date, however, is set to the date I originally started it, and ATOM sets the update date to the date finished or last edited.  Enjoy.

You may have noticed two things on my blog of late.  First is a Comment link that is simply a mailto: tag.  I have decided to use TC's method of comments for the time being until I can get a real system up.  Anybody have a problem with a port22 address?  Yeah, thought so.

Second is a hit counter.  I don't really like them myself, but I wanted to get some idea of the (really low) traffic coming here.  I know a couple people occasion, but I am a bit curious.  Honestly, I miss the traffic logs from my last job enough to want to do some of my own.  Kind of crazy, I know.  Anyway, it's just a little image that loads from a remote site in order for me to get an idea of views regardless of viewing from an aggregator or direct page views.

If you don't like either one, drop a comment!!