- Artykuły z tagiem static code analysis

Dzisiaj chciałbym podzielić się zestawem reguł, który w różnych projektach stosuję od lat. Pod to stworzyłem repozytorium Korzystam ze StyleCopa od ładnych kilku lat. Jest to niezbędne narzędzie gdy stosuje się Code Review. Po prostu szkoda czasu i ludzkiej cierpliwości, żeby ręcznie wytykać komuś coś, co może wychwycić narzędzie.

[StyleCop] od jakiego zestawu reguł wystartować – Show me the code

Narzędzia 566 dni, 20 godzin, 32 minuty temu https://krzysztofmorcinek.w... 97 źrodło rozwiń

Static analysis is a powerful feature of Visual Studio that helps us to spot syntax and semantic errors in our code. It works very well on currently edited file and runs on the whole solution as one of the compilation stages. But it would be a waste of time to run compilation every time you make changes that affect code outside currently edited file, only to check that you didn't cause any compilation errors. Luckily, Resharper comes to the rescue with...

Dziel się z innymi:
[EN] DemonBox - Hunt your bugs in design time

Narzędzia 1634 dni, 13 godzin, 59 minut temu cezarypiatek 76 źrodło rozwiń

In 1994 Robert “Uncle Bob” Martin proposed a group of object-oriented metrics that are popular until now. Those metrics, unlike other object-oriented ones don’t represent the full set of attributes to assess individual object-oriented design, they only focus on the relationship between packages in the project.

[EN] Object-oriented metrics by Robert Martin | Future Processing

Inne 1930 dni, 19 godzin, 38 minut temu FutureProcessing 182 źrodło rozwiń

One can ask why we need to think of CR practices at all. Review of code written by another team member can be done without any preparation or introduction. It is true, but there are some aspects that we need to think of. In my opinion, we especially need to support the following values:Quality – Code Review should be done in the same way, no matter if you are hurrying, bored or it’s your 3rd hour of doing CR,Motivation – team has to see value in Code Review, and this value shouldn’t be lost because of ne...

[EN] Yet Another Code Review Best Practices | Future Processing

Sztuka programowania 2105 dni, 12 godzin, 17 minut temu FutureProcessing 184 źrodło rozwiń

There are a lot of aspects to be considered while developing real world applications. Maintainability, Understandability, Clarity, Dependency are just a few of them. We have to work hard to maintain our code and make it self-commenting, preserve it from cyclic dependencies between assemblies or simply, to provide its good quality. There are a lot of tools that may help to achieve these goals e.g. Sonar, ReSharper, JustCode or NDepend. This article explains how to analyse the quality of code with the use ...

Dziel się z innymi:
[EN] Analysing the quality of code with NDepend | Future Processing

Narzędzia 2229 dni, 20 godzin, 24 minuty temu FutureProcessing 91 źrodło rozwiń


(32 895,6)
(32 816,53)
(27 178,29)
(21 178,88)
(20 336,33)
(13 018,14)
(10 526,6)
(9 775,28)
(8 478,28)
(6 837,96)
(6 214,22)
(5 393,84)
(4 157,41)
(4 026,73)
(3 908,07)
(3 599,64)
(3 448,35)
(3 318,39)
(3 224,66)
(3 206,43)