To SQL Masters: MAK, Skhanal, Ramiro...

In a recent article <<Don' Get Left Behind>> written by Brian Knig(http://www.sqlservercentral.com/columnists/bknight/dontgetleftbehind.asp
), he presented the following 3 key tips to keep up with the SQL server's evolution.
"Here are a few tips (in order of importance) to becoming a hybrid:

Learn XML - If there is one technology that a DBA must know in the next few years it is XML. SQL Server and other products of all kinds are integrating XML into their system. Not being able to speak this language would be equivalent of not understanding SQL in the next few years.
Learn CLR - A hybrid DBA will be expected to know at least one other programming language. These languages will be tightly woven into stored procedures in Yukon and much of SQL Server will go untapped if you're not up on these.
Learn DTS - The minute you cut a 2-week project into 2 hours by creating a DTS package, your stock rises. Developers will think of you as a peer, not a road block."

What are you SQL knowledgeBase people think about it? Personally, I have not touched XML, is learning CLR and only the simplest DTS without global vaiables. Most of my daily jobs are t/sql developement, though the part I enjoying the most is the data modeling.
------------------------------
XML: still don't see it as important as SQL. And where I am going to use it in a 100% windows environment?
CLR: I begin to learning VB.NET and ASP.NET so that to have some front-end tools and WEB presentation on 100 servers and 1500 databases size, activity, job running result, index-defrag... But how could I handle the coming C#/C++ code in the coming SQL2005 as whole or part of the stored proc if I don't know nothing about C#/C++? Probably I have no way to learn them too....
DTS: have to dig in deeper to dynamic level. Right now, use dynamic t/sql to cross 100 servers to get all neccessary info.

Am I in the right direction for the coming wave?

thanks
-D