This week's Advisor is about distance learning, one of my favorite subjects and one of my favorite pursuits. Living as I do -- off the beaten track -- the ability to access information makes it possible for me to remain current on a lot of things. In my case, as with billions of other people who live off the beaten track, learning at a distance is wonderful and amazing.

The year 2003 is shaping up to be the one in which companies will decide whether to embrace open source software or fail to adopt it and allow Microsoft to extend its control of desktop deep into the enterprise.

One of the biggest challenges of systems development is getting to the "root" of business requirements and associated rules. Often, I find that when moving from an existing system to a new one, business area representatives often present existing "workarounds" as business rules. As systems specialists, we need to recognize these false requirements and clarify the true business needs.

Sitting here reading a news item that reports that Oracle and SAP plan to release new analytic capabilities for their respective enterprise resource planning (ERP) applications (Oracle Financials and SAP R/3), the first question that comes to my mind is: Where have they been?

As we all know, achieving IT and business alignment is not easy. We must tie business strategy, technology, and people into a comprehensive and synergistic package that, as Paul Strassmann says, will demonstrate a positive relationship between IT and accepted financial measures of performance. However, as my mother used to say, you need to be careful for what you wish for, because you just might get it.

I read an interesting interview with Brian Arthur, a Santa Fe Institute theorist who studies technology revolutions. He argues that we had a big bash in the late 1990s and are now in the doldrums. But he also says he expects that 2003 is the year we start a new expansion.

More hours worked doesn't mean more work accomplished, especially in information work. Get tired enough, and you'll actually remove value from a project because of increased defects, missed opportunities for design improvement, and snappish or withdrawn behavior that strains the social fabric of the team.

Cutter launched its Enterprise Architecture Advisory Service in 1999. It seems appropriate to begin the new year with a brief survey of where this field has come in the last four years.

The most common method of software estimation, according to a recent survey by Cutter Consortium of more than 100 software development organizations of varied sizes, is the very basic technique of using the rough judgment of experienced developers -- the "guru" method.

The management of risk is like driving a car -- everyone believes they do it really well, but very few people actually do so.