Thumbs.db *.obj *.exe *.pdb *.user *.aps *.pch *.vspscc *.vssscc *_i.c *_p.c *.ncb *.suo *.tlb *.tlh *.cache *.ilk *.log [Dd]ebug*/ *.lib *.sbr obj/ [Rr]elease/ [Dd]eploy/ _ReSharper*/ [Tt]est[Rr]esult*/ [Tt]est-[Rr]esult*/ [Tt]emp/ [Pp]rerelease/ [Ll]ogs/ UpgradeLog*.XML _UpgradeReport_Files/ bin !SharedLibs/NUnit-*/bin/ !SharedLibs/NUnit-*/bin/net-*/*.exe
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult."
Tuesday, 16 October 2012
My standard .gitignore file for .Net projects
Saturday, 13 October 2012
So, what's your team's bus factor?
5whys.com is a site I've been enjoying recently and anyone interested in team leadership should check it out. I've just been reading one of Roy's posts about something called 'Bus factor'.
Bus factor: An irreverent measurement of concentration of information in a single person, or very few people. The bus factor is the total number of key developers who would need to be incapacitated, as by getting hit by a bus, to send the project into such disarray that it would not be able to proceed.
My team's daily stand ups, pair programming and the willingness for team members to share their knowledge means we certainly have a bus factor > 1. So, what's your teams bus factor?
Tolerance and the Equal constraint in NUnit tests
Those pesky tests that fail every once and a while because something took slightly longer than usual. Sure you could just run them again and they probably pass a second time round. There is another simple way to avoid this, the NUnit Within modifier for the Equal constraint.
[Test] public void CreationDateTimeIsSetOnConstruction() { var timeObject= new TimeClass(); Assert.That(timeObject.CreationDateTime, Is.EqualTo(DateTime.Now) .Within(new TimeSpan(2000))); }