Have you seen StackOverflow.Com yet? Go check it out then. While your at it, you might want to check the WPF questions on it. Although WPF is not one of the top tags, there are still some interesting questions ... and answers obviously.
Stackoverlow aims to be a wiki-faq-forum hybrid in which you can find answers to questions you have but instead of regular forums you don't have to browse through oodles and oodles of off-topic responses to find the best answer. Instead, the rating system should make sure the best answers 'bubble up the stack'. Nice!

After reading Rudi's posts (see my post from yesterday), I've decided to get to know Prism/CAG a little better myself. So, I will brace myself and start plowing through everything on the MSDN landing page. To recuperate from all the reading I might also watch Composite Application Guidance for WPF: Prism Goes Prime Time Webcast which seems pretty interesting and covers most basics! Prism... here I come!

Lucky for us Rudi Grobler has 'been tasked with' learning Prism, the Composite Application Guidance for WPF. Lucky, since he shares all his experiences on his blog so we can learn with him. According to him:

This is truly my idiots opinion about what I have learned trying out PRISM!

Well I consider myself an idiot as well (and damn proud of it), and found his posts so far pretty interesting :)

Here's the list:

Learning Prism
Learning Prism - Redux
Learninng Prism - Modularity

I've been reading Jesse Liberty's Silverlight Geek Blog for quite some time now and have occasionally linked to a few of his articles as well. Good news for us mere Silverlight and WPF mortals, because he's committed himself to

have a meaningful blog entry published every day by 1pm Eastern (GMT –5). By every day I mean… every day.

He's been at it for a couple of days and already posted some great articles such as Isolated Storage Might be Easier than you think!

Greg Slechter has a post on doing some wacky bitmap Displacement mapping, using a custom effect. It looks nifty and you get to use the aptly named

this.DdxUvDdyUvRegisterIndex = 6;

which gives you the feeling of being extremely 1334 1337!