Last week, I removed my VS2010 beta installation and installed VS2010 RC. The RC is much more stable, and as a bonus renaming a feature in a SP2010 project now works.
We have been building lots of features lately, and I was very pleasantly surprised to see this bug already fixed.

This tool makes contenttype development a lot easier.

Click the contenttype together in MOSS and copy the xml from this tool into your sharepoint solution.

This tool works with SP2010 beta.

http://www.codeplex.com/MOSS2K7CTypesViewer

A really nice (and funny) article why you should not do this, by Tyler Holmes.

http://blog.tylerholmes.com/2008/10/don-set-your-sharepoint-app-to-full.html

I came across this article because we had an assembly containing a feature reciever that would cause an error when executed.
Assemblies containing feature recievers should always go in the GAC (by design), but we where creating a custom policy.

So, I agree with Tyler that custum policies are still preferable, but when you have a dll that contains a feature reciever, you should just put it in the GAC.

Today I came across a iPhone app that enables you to browse SharePoint from your iPhone.
Haven't tried it myself because I use a windows mobile phone, but might be usefull for all you out there.

http://www.spyk.com/Products/iShare/Pages/iShare.aspx

Just thought I'd share...