I didn't know which metaphor to go with, as Learning to code through osmosis and The Virtual Mentor were other options.
I'm talking about my experience with dbvt.com/blog .Text source (and nGallery and DNN) where I work in the VS.NET project source to such an extent that I start approaching coding like the original author, in this case, like Scott Watermasysk. Someday I'm going to know how to pronounce his last name correctly. I'm NOT suggesting I'm going to suddenly start coding with the native skill of Scott or Jason A, but I'm approaching writing code like they do. And thus the metaphor.
One design construct of .Text 0.95 that I am now very locked-in on is the Provider model with Business Object Collections. The Provider model is a staple of both DNN and nGallery, but I've been able to spend more time with .Text than the others. (If you want the best introduction to the provider model I recommend Jason A's nGallery source, where you can quickly grasp how he supports switching between XML and SQL data sources.) There's more to Providers than being able to switch the data source, of course, and I suspect it is a first cousin to Rocky Lhokta's CSLA (though I've not yet bought the book. I will! I will!) But its one of those practices and evolutions in the design of your coding that makes you feel good about what you're doing and how you're doing it.
So I'm starting a new project this week and know without a doubt that I'll be using a provider model. And a ton of stored procedures. And lots of those fun Collections!