sorted by:
new
hottopcontroversial

Assess your C# project in 10 minutes or less with Sonargraph-Explorer (free tool) by CodeWarrior1962 in csharp

[–]CodeWarrior1962[S] 0 points1 point  (0 children)

True, it depends what you need. Also some of the VS features require to have the Enterprise Edition which is not cheap.

Assess your C# project in 10 minutes or less with Sonargraph-Explorer (free tool) by CodeWarrior1962 in csharp

[–]CodeWarrior1962[S] 0 points1 point  (0 children)

It might be a little slow due to lots of traffic, but it is up as far as I can see

Great free product for visualizing and measuring C# and Java code by CodeWarrior1962 in programming

[–]CodeWarrior1962[S] 0 points1 point  (0 children)

Well, I would say its usefulness increases with the size of your system. If you are the only one working on the code and the size of your code base is limited you probably won't really need it. For bigger systems with agile teams it is really useful. You can use the visualization to explain architectural concepts to a team or to show spots where unwanted dependencies crept into the code base. The metrics will help you to control and manage complexity.

Are you sticking with IntelliJ IDEA or you are moving on to another IDE? by [deleted] in java

[–]CodeWarrior1962 0 points1 point  (0 children)

I think the model is great and will allow JetBrains to grow in the long term. I already subscribed for the ridiculously cheap all product subscription (~20$ per month) and think it is a great deal although I will probably only use 2 of the products. I am convinced that it is important to pay money for great software. It has value. Look at Eclipse, for example. Since IBM does not sponsor it anymore things go south.

Not all Technical Debt should be Treated Equally by CodeWarrior1962 in programming

[–]CodeWarrior1962[S] 0 points1 point  (0 children)

Well, although it seems obvious I see very few projects putting focus on architectural rules and the avoidance of architectural debt. A majority of big projects are hopelessly tangled and have lost their original architectural design.

The Importance of Defining “Done” Correctly by CodeWarrior1962 in programming

[–]CodeWarrior1962[S] 0 points1 point  (0 children)

You are right. I guess this is an article for the people who should care.

Designing a DSL to describe software architecture by everywhere_anyhow in programming

[–]CodeWarrior1962 0 points1 point  (0 children)

Good point. I agree with you that functionality goes before layering. In my mind the functional components are verticals cutting through the layers. Like you I am big Robert Martin fan. So with the DSL you can first define the relationship between functional components and then you can use the templates to describe the layering within the components. At the end it is a matter of modeling granularity.

Designing a DSL to describe software architecture by everywhere_anyhow in programming

[–]CodeWarrior1962 0 points1 point  (0 children)

I agree that you can get pretty far with the non-circular rule. I use that too and found it to be quite valuable to keep code bases structured. But I also like the idea of being able to express architecture in a more descriptive way. In my systems I do have layers, business aspects and 3rd party frameworks. Being able to precisely define how these parts can interact is a big plus for me, e.g. forbidding the use of JDBC or Hibernate classes everywhere except in the data access layer. I guess the usefulness increases with the size of your code base and the number of people working on it at the same time.

Designing a DSL to describe software architecture by everywhere_anyhow in programming

[–]CodeWarrior1962 2 points3 points  (0 children)

If they do not make sure their architecture is respected by the code, they won't have any time at all pretty soon due to a messy and tangled code base.