Best Practises and Guidelines for SharePoint 2013 Development

Question

Currently We are using SharePoint 2010 and doing a lot of enhancement and customization in the portal.
we are planning to migrate SharePoint 2013 after 6-9 months.
I want to know what are the best practices and guidelines for development in SharePoint 2010 keeping one thing in mind that customization should be compatible or can easily migrate to SharePoint 2013 so that re-engineering effort would be as minimum
as possible.
We have every possible piece of customization in SharePoint 2010 portal like web part, event receivers, workflows, master page, page layout, custom search etc.
Please do the needful.

Answer 1

Best practices don't really apply here. They are generally rules of thumb that you can apply without thinking too much and be pretty much right. Development is by it's nature too varied to allow that sort of best practice guidance.
Having said that the main thing you should be concerned with around the choice of development approach in 2013 is the intended future of your client and the application. If they are making a move to the cloud you should be concentrating on the app model
and rapidly phasing out farm solutions. If they are considering it then you can still consider using the more old-school options of farm solutions and sandboxed solutions. If they can't go to the cloud because of data security etc. then you are more or less
free to use what you like.
Also, try to move to client side processing wherever possible. MS are only going to make server side work less pleasant in future.
Beyond that, get to some conferences and start chewing through some of the blogs on the topic.