Message-ID: <738390884.191.1432714500836.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_190_1498184337.1432714500835" ------=_Part_190_1498184337.1432714500835 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Like Bugs and Potential =
Bugs, Coding Standards Breaches are tracked through the issues mechanism. While it's difficult to ma=
tch each of the seven deadly coding sins to an analogous deadly spiritual s=
in, you might associate this sin with sloth - because transgressors ar=
e too lazy to learn and follow your team's standards about whether or not t=
o use spaces in
if statements. But it may be more appropriate =
to match this coding sin to the moral sin of pride - pride that the si=
nner's code is so good he don't need to be bothered with which line you and=
your teammates all agreed to put the curly brace on.
Another, perhaps more serious example of this type of sin is the failure= to follow naming conventions. Flout the industry standards about naming co= nstants in all upper case, and you invite the coders who come behind you to= fall into the kind of subtle bug that can be very hard to diagnose. <= /p>
Wherever the infraction falls on the curly brace-to-upper case continuum= , this sin is about not following the team-agreed standards. And that lack = of compliance means that other people on the team will be tripped up when t= hey try to read this non-compliant code, and at best spend extra time just = trying to parse out what's happening - time that could have been used for m= oving the code base forward.
To monitor the compliance with coding standards, add the Issues and Technical Debt widget to your <= a class=3D"unresolved" href=3D"#">dashboard:
It is possible to check compliance with coding standards on both source = code and unit tests code.
Use the differential views to mon= itor new issues.