Category Archives: Team Building

The topic of this post sorts reminds me of the whole DbC mess that paralyzed our group for years. Wow, the fallout from some key bad decsions! Well, this example is much more harmless, but I thought it was interesting. … Continue reading →

History: After some time, I started getting the idea that the evolved code review process may not be so good. Basically, team members use SD Pack and email. Everyone on the team gets the email and everyone sends the review … Continue reading →

LINQ is basically a translation layer between the class paradigm for programming languages and rows in a relational database. Instead of the programming languages using SQL to query the database, they use instances of their classes and LINQ together. LINQ … Continue reading →

If I were to answer the question, “What are the elements of a worthwhile code review?”, to a IT reporter in need, I would answer something like this: A proper code review is a valuable tool to any software team. … Continue reading →

In the US, when someone asks, “We don’t have any bugs in our code, do we?”, we answer “No” (OK, don’t get too caught up here in the fact that all software has bugs somewhere.  That “no” is the normal … Continue reading →

I was thinking about this the other day… If there was one skill that members of the team could have to ensure their success, what would it be? Of course, technical ability, communication skills, blah blah, those are all very … Continue reading →

From an exhibit in Leading Change by John P. Kotter Management Planning and budgeting: establishing detailed steps and timetables for achieving needed results, then allocating the resources necessary to make it happen Organizing and staffing: establishing some structure for accomplishing … Continue reading →

I noticed simple communication mistakes and inefficiencies today. Here are the ones that I can remember. Now, imagine this multiplied over every day and over email from the US. Email instructons: “From the dpgcmd project, take the files MediaCommands.h and … Continue reading →

I have a three recent examples of Extreme Programming failure, specifically “Collective Code Ownership”. Some of these examples are serious. Collective Code Ownership means that everyone is responsible for all the code. Any developer may change any part of the … Continue reading →

The perception: A Redmond development team in gets in to trouble and needs help with fixing bugs. The MACH SW Team has functioned as a bug fixing house before, so we follow with tradition and send the bugs across the … Continue reading →