I'll suppose this is really "ask me ANYTHING", I was looking for a long time, for an answer to this question:
Can EF code first replace all database-centric features like stored procedures, views, UDF.. Etc, and still maintaining high performance?
You can ask me anything, but that doesn't mean I'll have a useful answer. I'm afraid I know very little about EF myself. I can see a place for stored procs where logic is required "close to the data" but in my former roles where I actually used SQL in business apps, I still preferred to avoid them where possible.