Unusual Attitudes

Rich Stowell

Rich is a real hoot. He is the national CFI (Certified Flight Instructor) of the year for 2006, and he's one of those instructors who knows his topic inside-out. I could ask Rich any question about the airplane -- say, "What would happen if you cut off the engine all pulled on all of these levers here?"

Rich would say something like, "Let's go try it!!"

And we would. At the end of those 20 hours I had a better understanding and control of the airplane I was flying. I didn't lose all fear -- fear is what keeps you alive. But I flew better and I was a better pilot. It was time well spent.

What are you seeing? What are you thinking?

One of the things I observed about Rich did is that we talked about what I would see, what I would think, and what I would do while we were on the ground. To translate into computer-ese, we were talking input, processing, and output.

Once we got in the air, there were no surprises. Things happened just like Rich said they would, and eventually I learned to process the stimuli and respond correctly automatically. It got so that not only was I not afraid of spins, I actually enjoyed them. Rich could say something like "make the plane spin 3 and a half times and end up pointing that way." and I could do it. I flew spins, loops, hammerheads, rolls. I even flew the plane upside down for a while!

I remember the first time we did spins. After Rich recovered the airplane, he asked, "I know this all happened very fast, but did you see anything during that maneuver?"

"Yes, " I responded, "I saw my life, flashing before my eyes!"

I think making software is a lot like my epxerience flying airplanes. You start out knowing a little bit, maybe enough to get a job and make some bucks. For a lot of folks, that's all they want, so they get into "coast mode." Some, like me, try harder and harder technical tricks. Then they try management. Then they try large-scale architecture, or program management.

I invented the MAT as an instrument panel for software projects. In my opinion, if we can start learning that "input, processing, ouput" while we're making software projects, we'll do a lot better. The MAT gives the software team an input on what processes are working and what processes are not working. Once you've got some objective instruments, you can start learning how to think about what you are seeing.

Most teams do not do this. Instead, one guy sits around collecting status reports on Friday. Then he compiles them into another report and sends them to his boss. This is what takes the place of "flying the project"! It's like all of our projects are on autopilot. When they go off the rails, sure. Then there is a lot of yelling and stress. But does anybody take a look at the instruments? Nope. Instead it's pet-theory time. If your project is hosed, you can bet that you are going to learn your boss' pet theory about "why software projects fail." Better hope it's a good one.

Strap on the parachute and harness up! We're going for a ride in a Pitts Aerobatic Biplane

Another lesson I learned was that you always train outside of what you expect to accomplish. If you are interested in just being a Java web developer, you should probably learn some database and project management skills. If you are a project manager, you should learn some coding and some program management skills. Sure -- you might never expect to use them, but having the knowledge of what happens outside of your little box makes you a better team player. It gives you confidence, and keeps you where you want to be in your career.

I like aerobatics so much that after I got my instrument rating (you didn't think I would simply stop learning, did you?) I went back out and had Rich teach me some more advanced aerobatics. This time we went up in the Pitts, which is an awesome behemoth of a plane. Flying it is like dancing with the devil. I had a tremendously good time.

You should try it some time! Tell Rich that Dan sent you.

Looks like problems ahead in Integration and Scope Management. Is your team ready?