I've got an irrational hatred of views on tables from sorting out various endemic performance issues with systems which were essentially not very well designed. I acknowledge it was the bad design bit that was the problem but still harbour a strong dislike of excessive view deployment (of course views can be very helpful in some circumstances).

As to stored procedures, I find they quickly get overly long and impenetrable, and the business logic they contain can often be better (more clearly and elegantly) expressed in code e.g through EF. This is obviously for the types of systems I have written and with my knowledge set and experience of the other developers I have worked with and I accept it's not gospel. Clearly this does not preclude the use of procs where they are the best choice for the job.