-
Archives
- May 2013
- February 2013
- October 2012
- August 2012
- June 2012
- May 2012
- March 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- June 2011
- May 2011
- March 2011
- February 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
Category Archives: Maintainability
A typical effect of setting CopyLocal = true
If you read me in the past, you certainly know that I have a problem about the Visual Studio default option that set CopyLocal = true in project references assemblies. I mean this option: I’ve already explained the problem in … Continue reading
Don’t assign a field from many methods
For the next NDepend version, amongst plenty of cool stuff, a new default code rule will be added. It has been named Don’t assign a field from many methods. It falls into the category of Purity – Immutability – Side-Effects rules, one of my preferred set … Continue reading
Also posted in C#, high cohesion, Immutability, measurement
Leave a comment
Ruling Code Quality Regression
A prominent characteristic of the software industry is that products are constantly evolving. All modern development methodologies prone that a product should evolve through small iterations. Internally, development teams are using Continuous Integration servers that shrink increment length to a … Continue reading
Maintainability, Learnability, Component, Layering
Normal 0 21 false false false FR X-NONE X-NONE The last ayende’s post contradicts everything I know about software. Ayende goes against the idea that maintainability can be measured by how easy it is for someone unfamiliar with the code … Continue reading
Also posted in Ayende, Component, Layering, Learnability
7 Comments
Re-factoring, Re-Structuring and the cost of Levelizing
I think there is a clear distinction between re-structuring and re-factoring code. This is because of the nature of the OOP code which is made of 2 distinct artifacts: methods’ bodies and fields on one hand, and methods’ declarations, types’ declarations, namespaces’ declarations on the … Continue reading
Dealing with Code Un-Coverable by Tests
Code UnCoverable by Tests Even for test-coverage addict (as me), there is some code that simply cannot be covered by tests. An example? The call to MessageBox.Show() cannot be tested automatically since it is blocking. Of course we could mock calls to MessageBox.Show(), … Continue reading
Also posted in Code Coverage, Code metrics, CQL, CQLinq, LoC, measurement
7 Comments
The Open/Closed Principle on MSDN
My latest article entitled The Open Closed Principle is available in the June 2008 edition of MSDN Magazine. I tried to present both the motivation for following the OCP and some design strategies (besides the obvious Plugin example) and related … Continue reading
Put Code Where You Would Expect to Find It
I’m going to propose a new design concept with an admittedly awkward name called the “Put Code Where You’d Expect to Find It” Principle. It means exactly what it sounds like. A team should strive to consistently put different … Continue reading
Jeremy’s Fourth Law of Test Driven Development: Keep Your Tail Short
One of the first ongoing lesson for making Test Driven Development succeed for you is to learn how to write isolated tests with less effort. My Fourth Law of TDD is all about recognizing the need to do testing piecewise … Continue reading
The Don’t Repeat Yourself Principle and the Wormhole Anti-Pattern
Getting back on track with the "Maintainability" series of posts. I'm doing this way too late at night, so the coherence might be lacking. Don't Repeat Yourself Don't Repeat Yourself (DRY) is a statement exhorting developers to avoid duplication in code. … Continue reading