Comments on: Developing for Maintainability

By: Naruto

Naruto — Sun, 21 Mar 2010 17:41:31 +0000

Hallo
Geniales Post. Da hat mich Yahoo wie schon so oft an einen super Blog geschickt.
Viele Grüße aus Monheim am Rhein

By: Jens Schauder

Jens Schauder — Tue, 22 Dec 2009 09:23:46 +0000

CRAP4J is definetly a viable alternative to toxicity. It has the benefit of better tools support I'd say, but It considers only two base metrics (cyclomatic complexity and test coverage). I like to keep the later seperate, but I guess it is all a matter of taste right now. Interesting combination: toxicity, crap and taste ... I don't know about Visual Studio Tools. But the only thing you realy need is some static code analysis tool like checkstyle. The rest is almost trivial. And a quick search turned up this wikipedia page as a good starting point.

By: Stefano Ricciardi

Stefano Ricciardi — Tue, 22 Dec 2009 07:21:33 +0000

The "toxicity" seems like an interesting concept. Are you aware of any tool or plugin for Visual Studio can calculate it for C# code? Uncle Bob blogged about a maintainability measure that also takes into account test coverage, called CRAP. That is an interestic metric as well.

By: Tweets die Schauderhaft » Developing for Maintainability erwähnt -- Topsy.com

Tweets die Schauderhaft » Developing for Maintainability erwähnt -- Topsy.com — Mon, 21 Dec 2009 09:01:35 +0000

[...] Dieser Eintrag wurde auf Twitter von Jens Schauder und A. Ebbert-Karroum, Benjamin Winterberg erwähnt. Benjamin Winterberg sagte: RT @jensschauder: New blog post: Developing for Maintainability http://blog.schauderhaft.de/2009/12/20/developing-for-maintainability/ [...]

By: DingensBummens | Das Ding was Bummst » My Google Reader Shared Items – Sunday, December 20, 2009

Sun, 20 Dec 2009 17:10:18 +0000

[...] Developing for Maintainability [...]