Manhattan for Windows

User Reviews

• See the quality of a whole project's source code in one snapshot

  January 8, 2003

  Pros

  Cons

  Summary

  For what I learned, two kinds of people are concerned with quality of the source code: - a few responsible developers (and therefore *good* developers) who know what dirty code will bring in the end to a software product - a few clever managers, who know exactly the same thing. Unfortunately, I never saw any of these two kinds use a systematic way (or tool) to actually monitor source code quality. The reasons of this are: - the developers don't want to waste their time with a complex tool that will not tell them anything new about their code ("I know what's in my code") - the managers (if they have enough time) have problems to understand the output of such tools. By the great idea of showing the source code in the metaphor of a town, Manhattan solves both problems in this way: - The developers can see in one second where are the dirty parts in a whole project. They can then zoom-in to see detailed information about what is wrong and where. Globally, the snapshot of the town could even make them feel proud of their project's quality... - The managers don't need any technical knowledge to use the tool nor to understand the global result. A poor quality source code will show a town looking like Gotham city (tall, darks buildings, no green spaces). A good quality source code will look like Beverly Hills (small, bright buildings, grass everywhere, swimming pools). In fact, this is my only critics to this program: if the town representing your project actually looks like Manhattan, it means a very poor quality for your code... May I suggest to rename the software?...

  ---

• Show reviewsHide reviews
• Rate it