One of the most frustrating things to me is seeing developers doing new things, but in "old" ways. A classic example is one you may have seen yourself: Here we have a sophisticated client - side application that runs in Internet Explorer, we use XML Data Islands and XSLT transforms and parameters, templates, and we even use XMLHTTP from the client. And along with this we may have page upon page that needs to get a recordset from SQL Server - sometimes many recordsets, and bring them into the page as XML so we can do all our "new kind of cool stuff" with it. Well, that's great.
When you have to work with HTML controls in a web-based application, 100% of which are populated and whose properties are set via dynamically-generated XSL transformations at runtime, you get to be pretty inventive. And one of the first things you learn is how NOT to "reinvent the wheel". That is to say, if there is an example somewhere or some existing code that you can borrow from or re-use, there is "no shame and no blame".
Usually we use an ASP page with Javascript or VBScript inside it to either get data from, or put data into SQL Server. However, from time to time you wish you could run that favorite, most useful ASP page that you've written that does all those great things and instead have something that happens in SQL Server cause the call to the page.
At EggheadCafe.com, we have resources that are added on a daily basis - both by member visitors and by the staff. These resources are searchable and are broken down by categories such as Hotlinks, Articles, Tips & Tricks, etc. Each evening , we have a script that's kicked off by the NT Scheduler service at a time when traffic is normally low, that scours our resource database for the most recent items in each category.
I regard myself as a particularly fortunate "XML Dude": About a year ago, I determined that, regardless of the amount of time I had in the day, and regardless of the fact that the company I worked for at the time had virtually no vision as to what XML could do to help solve their problems, I was going to spend some time -- for ME -- each evening, studying this new technology and learning how to use it.