Easy way of making something simple hard.

Thanks to r# we do not need to add interfaces for internally accessible code unless there is a need for it. Of course this is not the same if the interface is an implementation (or part of) of an externally visible api.

Sometimes change hurts. You know what I’m talking about if you need to change the multiplicity of a relationship (let’s assume you talk about an ordinary sql database). For instance: From 1 to 1 To1 to many For instance, say it’s an adress. The assumptions made when there is only one adress permeates throughout the applications. For instance a person must have bills sent to a different adress (his/her accountant or something similar). However, when contacted, any mail needs to be sent to the home address.[...]

How many times are you writing these keywords? For many of the things I write I don’t feel that these keywords add to the readability of the code. It would be sweet to be able to specify on for example assembly level the default visibility of your code. Or perhaps some short version of the keywords? $ class Comment { _ id; //private $ Id { get{ return id;} set{ id=value;} } //public @ someValue = “”;//protected } Or let the visibility be govern by name convention if you set some flag in assemblyinfo.cs[...]

I’ve played around with branching and merging in git. It looks like a useful tool. In the current project we are maintaining two different branches right now. I can see that it would be useful to be able to use the functionality in git/mercurial to help me merge and cherry pick.HERDING CODE 96: ERIC SINK ON VERACITY AND DVCSHanselminutes Podcast 231 - Eric Sink on Distributed Version Control Systems