The Truth about 911 – A Video

Aside

A one hour analysis of 9/11 and how it is more likely than not that the government was actually behind the attacks. I heard about this on Adam Curry’s Daily Source Code. This is a really well done documentary. No matter what you believe, you’ll be fully engaged by watching this video. This one is going to cause me to leave the house an hour after I scheduled myself to leave for work this morning. I’m totally sucked in.

The Build Master: Microsofts Software Configuration Management Best Practices

The Build Master : Microsoft's Software Configuration Management Best Practices (Addison-Wesley Microsoft Technology)Saturday by chance at Borders I ran across the book The Build Master : Microsoft’s Software Configuration Management Best Practices by Vincent Maraia. Vince has been a member of the Microsoft build team for 5 years. Since this is the first book I’ve ever seen on this subject (not counting Pragmatic Project Automation, which is very Java specific), I decided to start leafing through it. After a bit, I decided to pick it up as it looked like it had some really interesting information that I would want to actually take home and go through in detail.

I guess the biggest thing that I have learned while reading this book is Microsoft platform based software is highly complex and that there is no real “nice” way to just buy a buiild system for the software. The other thing I learned is that Microsoft as a company actually takes this piece of the process serious enough that they fund a team to do it and I believe at one point Vince points out that the Microsoft build team is around 60 people. They recognize the cost savings that are possible in having a team managing this stuff rather than just letting the developers do what they need to do in order to get the software built – something quite refreshing to hear.

Vince goes through quite a bit of detail in how Microsoft manages their build systems, how they throttle checkins during release mode and have bugs move through multiple levels of approval before being allowed to be moved into the main source base.

One of the most interesting pieces of the book is where Vince explains the organization of authority around the build teams. Apparently, at Microsoft, the build team is actually the team that is responsible for rolling out new build tools and versions of the build process to the development teams and are expected to schedule and facilitate the release of new build processes after each software release. They schedule when new toolsets are migrated into the build environment, not the development team.

The build team also has complete control of their build machines – corporate IT does not. They have structured the ownership of the build labs so that they are completely in control of the build hardware, software and patches released to the machines and therefore are totally outside the corporate IT process for these machines. Vince talks about the importance of this structuring of authority and why it is necessary. Though when you read it it seems like one of those “duh” moments, its rare to find a book these days that actually supports and explains the reasoning behind machines needing to be outside the authority of corporate IT and why control needs to be given to the team for them.

Vince also goes through the new Microsoft Team tools and talks about some of their history and gives us a peek into whats coming up in future releases of these tools. The toolset looks really interesting and it seems as though Microsoft is actually taking the tools they have been using internally for years and productionizing them for release for others to use to manage the building of software in their environment. I guess time will tell as to whether these tools will be useful, but I liked the preview that Vince provides.

Some things I didn’t like about the book: Lots of focus on VSS, as apparently this tool is still used quite a bit at Microsoft. VSS has never been a valid revision control system to me and some of the techniques Vince talks about (like cloning trees and detaching them from the mainline for release branching) just struck me as inefficient. In my experience, as you fix bugs on a release branch, these changes have to be merged into the next release of the software (except in extreme cases where the next product is a completely different codebase like Windows XP vs. Windows 98) and this approach send you back to manual merge type of situations rather than merging between trees.

Overall though, this book is full of really great information. At the very least, you get a glimpse into the change management processes used in a very large company and an appreciation for the scale of a company like Microsoft and the problems they can have releasing software. You also get a good glimpse at the new tool sets coming from the Microsoft teams, which do sound quite interesting.

Just to give you an idea for the amount of information provided, take a look at this chapter breakdown of the book:

  1. Defining a Build
  2. Source Tree Configuration for Multiple Sites and Parallel (Multi-Version) Development Work
  3. Daily, Not Nightly, Builds
  4. The Build Lab and Personnel
  5. Build Tools and Technology
  6. SNAP Builds – aka Integration Build
  7. The Build Environment
  8. Versioning
  9. Build Security
  10. Building Managed Code
  11. International Builds
  12. Build Verification Tests and Smoke Tests
  13. Building Setup
  14. Ship It!
  15. Customer Service Support
  16. Managing Hotfixes and Service Packs
  17. Suggestions Change Your Corporate or Group Culture
  18. Future Build Tools from Microsoft

There are also four appendices: Embedded Builds, Extreme Programming (where Vince talks about Microsofts experiences in researching XP), Testing Guide, and Debug Symbols.

As an added bonus, the book is full of what Vince calls “Microsoft Sidenotes”, in which he uses real life situations at Microsoft to illustrate some of the points he is trying to make.

Overall, great book. There’s a lot of information to digest here. I’m definitely taking this one in and passing it around my team for review.

Movies: Hostel

Yesterday we went to see Hostel, a new “Quentin Tarantino Presents” film written and directed by Eli Roth.

I had not read anything on the film, so had no real expectations going in except for Tarantino’s name on the film. I’m a big fan, so I’ll basically go see anything his name is on. Aside from that, however; I knew nothing about the film at all, not even the basic story line. I would recommend you go into the movie the same way. If you have read any of the reviews on Rotten Tomatoes or other review sites, you might find that you know too much to be as shocked as I was and that in a vague way too much of the plot is given away, even on the non-spoiler sites.

Now, on to the movie. The movie is about two kids, Josh and Paxton, going to college who have decided to take a backpacking trip through Europe. Along the way they have befriended an Icelandic man named Oli and the three of them are making their way through the Hostels in Europe, in search of, you guessed it, getting high and getting lucky with European women. Josh has just broken up with his girlfriend, so Paxton and Oli are trying to get him hooked up with someone along the trip to help him forget his problems.

They go out one night in Amsterdam and wind up being out after curfew and cannot get into their Hostel. They are taken in by a guy who smokes some pot with them and tells them about a Hostel not on the usual maps where the women love American men and “will do anything for them”. This is enough to get the three trekking towards this off the map Hostel.

Once they get to the new Hostel and check in, they go to their room, which is shared with two women. They are invited by the women to go to the spa with the three women and begin to have a good time. The women are very “hospitable” and Josh and Paxton get lucky with their respective female roommate as Oli (“The King of Swing”) finds someone to hook up with as the night ends.

Then Oli disappears. Checking at the desk, the boys are told that he checked out early this morning. The boys are worried and try repeatedly to call and leave notes for Oli, but he doesn’t respond. They are shown a picture of him that has been taken showing he went off with the girl he met. The guys think this is weird, as he made no effort to let them know he was leaving — and the girls invite Paxton and Josh to go to the disco with them to distract them from their fear for their friend.

At this point in the movie, you are absolutely convinced that this movie is your typical “freaky homicidal maniac kidnapping and killing people” type of movie. It isn’t — not by a long shot — and that is all I’m going to tell you about the plot of the movie. The rest you just have to see for yourself.

Here’s what I will tell you. The twist of what this movie is actually about is on the order of the The Sixth Sense, but about 100 times more disturbing. As we were walking out of the theater I was completely quiet, trying to come to terms with what I had just witnessed. I have never seen a movie that I found this disturbing and that I had thought about so much after the ending credits had rolled.

So to get to the bottom line, here’s the review. The movie is totally worth seeing and I’d give it at least 3.5 stars on a scale of 4. Rotten Tomatoes currently shows a 69% fresh rating. I’d give it higher than that, as I think its definitely original and not the same recycled plot lines that you find in your typical horror movies. Its definitely unique and extremely disturbing. The movie is full of nudity and what seems like gratuitous violence. As the plot unwinds, however, the violence seems less gratuitous (at least it did to me) and necessary in order to communicate the gravity of the final destination of the plot line.

Normally, I enjoy watching horror movies with Kelsi. I would definitely sit down and watch Saw with her, another movie that I really enjoyed for its originality and total non-hollywood feel it had. I’ve yet to find a horror movie that I wouldn’t buy and sit down and watch with Kelsi if I liked it.

Until now. I don’t think I ever want to see this movie again. I don’t want to watch it, and I don’t want to own it when it comes out on DVD. I think it was a great movie, but the final destination of the plot line is something I never, ever want to see again — as it explores what I think is the darkest side of human nature and one that, quite frankly, I would rather kid myself that it doesn’t exist.

So for me, the movie was extremely satisfying, in a warped way. I finally hit my limit as to what I am willing to watch in a movie — but for different reasons that what I have experienced in the past. Normally, I am frustrated at wasting money on stupid plot lines or over produced special effects that are there for the sake of having the effects. I usually have a movie push the limits I have around feeling like I’ve wasted my time.

My limit here was completely different. This movie had an interesting plot, let you get to know the characters well enough to care about them and then pushed you right over the edge. The subject matter was such that it was real enough that it could possibly happen and yet so disturbing that you don’t want to think about the fact that it could actually happen, if that makes any sense. In some ways, I felt that the subject matter was just one of those things that should never be put on film, which is satisfying in and of itself.

I would definitely recommend that those who don’t find nudity and a lot of violence patently offensive actually go to see the film for the experience. I was pretty blown away by it.

Tickle Tests

I found a site called Tickle that has a slew of career oriented tests, many available for free after registration. I became curious so I decided I would take the time and take some of the tests, just for the hell of it. The first was the Right Job / Wrong Job test, which purports to tell you what kind of personality you have and therefore what type of position you would fit best in.

After taking the test, here are the results:

As an Analytical type, you don’t want to be limited by established rules and regulations. Your inquisitive nature demands that you sometimes question authority. Otherwise, you might not be able to find fresh approaches, or come up with new solutions to a problem. It’s not that you act without weighing the pros and cons of a situation — it’s more that you’re more willing than others to take justifiable risks if they’ll further your career success.

You’re smart enough to know when you need help and are confident enough in your abilities to ask for it. You understand that sometimes there are no clear right and wrong answers, and that’s just fine with you because you tolerate gray areas better than most. In fact, pondering potential outcomes can sometimes be more interesting than coming up with the definitive solution for you.

Your right job doesn’t have to be about self-expression, but it needs to be a job you can be proud of.

Is it accurate? I would say I agree with most of it, except that I don’t think I’m driven so much by furthering my career success as I am by knowing that I’m making a difference and creating positive results. I definitely feel that established rules and regulations limit the effect one can have in an organization, because in many instances the rules can’t be changed because they exist, no matter how much they don’t make sense in the current environment. In these instances I rarely have the patience to debate with someone who doesn’t recognize that the established rules and regulations go against common sense.

There’s a good leadership development opportunity for me …