Keep solutions simple and think about your deliverables Chad Myers at Los Techies tries to get a discussion about why it's bad to have to many projects:Project anti-pattern: Many projects in a Visual Studio Solution File Some of the consideration is about build performance. He is referencing microsoft blog posts... I know the lure of getting to drink coffee while waiting for builds, but you're not getting paid for coffee ;) There is an article on O'Reilly about the cost of long development cycles:Dead Tim[...]

You use mocks when you want to test how the code interacts with the mocked objekts. If you care mostly about the end result, the final state, then it's easier and less brittle to use fakes.

Listening to herding code on fluent migrator is quite interesting. You could read Getting started with fluent migrator. If you feel the need to contribute there is fluent migrator on github.

http://studiostyl.es/schemes/wekeroad-ink

Looks awesome for simple things:Simple.Data It's Rob Conery!massive The blog post and I shall call it massive. Might be used by stack overflow:dapper As described here:How I learned to stop worrying and write my own ORM