It’s been over 2 years in it’s current form and I really must get around to updating my website. As you can see, I went for a really retro “early days of the web” approach; possibly even with the caveat that it’s best viewed in a text only browser. So moving on, time for an update – I’ve not drawn up any designs, so that should be interesting but the site will probably just be . . .
Today Jetbrains announced on their blog that they’ve released a resharper nuget package that will obtain project references via nuget, rather than making direct references to the locally installed code. As we are currently in the early stages of transitioning from VS2008 to VS2012 we aren’t ready to start using NuGet(*) but I think I’ll be grabbing this plugin for when we do. (*) In my last role we were using VS2010 and making heavy . . .
Over the past couple of years I keep on coming back to Project Euler, it’s nice when you just want a quick challenge, or to try your maths skills. It’s highlighted how rusty some of my concepts were, and I’ve learnt a whole load of new ones along the way. I really like the way that the example problem given is quite quick to determine using brute force, but the desired answer always needs a . . .
There are many articles on the web about how to do good code reviews, with mostly all of them either discussing their merits or how to obtain maximum value from them. In a new role, I’ve recently helped introduce and roll out the agile process and to start with as part of each story we always added a task to “code review” all work. We made sure that differences from source control were used to . . .
Leading on from the previous blog post on reducing code noise when checking for null parameters, these help functions can be utilised to further reduce code noise that generally occurs in class constructors. Most constructors are purely made up of the following duplicated checking/assignment code. Again putting together a small helper function, making use of the previous Throw class can remove 90% of the previous argument checking/assignment code resulting in: Get the code from GitHub.
The problem with writing defensive fail early code, it doesn’t take long before methods are 70% argument checking, 30% logic: Code contracts can be a great way to move code out of the method body, but how can you clean up the code just through traditional refactoring? For the last few projects I’ve worked on, I’ve been using a small helper class that abstracts all the conditional code out, leaving just a single line call . . .