For code conventions we stick to:
http://blogs.msdn.com/brada/articles/361363.aspx

some principles I like:
  • Try to write clear and easy to understand code by means of good naming and clear structuring (easier said than done)
  • KISS (That does not mean the easiest and quickest solution, It can take a lot of thinking to come up with a simple solution)
  • Keep dependencies low.
  • Support a limited number of features and do it well. Be clear about what not
  • When things are done automatically there should be a manual override
  • If you need a lot of code to implement your solution think about it somewhat longer
  • I have to understand everything :)
  • Give lots of feedback, no right/wrong culture, talk about everything.

Last edited Apr 17, 2010 at 10:39 AM by pauldendulk, version 6

Comments

No comments yet.