Best working practices versus life
I noticed that people, lately, more and more often became very categorical: you need to create unit tests for everything (XP TDD), valid CSS above all (W3C validity), a standup meeting is needed even with a cleaner (Scrum) ...
Here I suggest you speculate on the topic Best working practices versus life!
A typical case: a mid-level project, the logic is quite simple, you have short iterations.
And you have a low error price, that is, you do not write a banking application where there is a chance to lose millions in the event of an error. It's like this: someone found a mistake, wrote to you, you said thanks and fixed it.
I respect Extreme Programming (XP), but I am not a supporter of TDD [ Test-driven development ] where you first need to create tests that describe the requirements for the code, before writing the code itself, so you need to create a test for each feature.
In my opinion, TDD increases costs without giving corresponding advantages in return (except for projects with a high cost of errors). It seems reasonable to me to find a balance and use Unit tests for critical application logic.
“Friends, how is it that you do not have valid CSS on the pages: ...”
from a letter to our company from a user of the service.
Yes, I love W3C validators [ W3C the validators ] but when confronted with the convenience against W3C validity choose convenience.
An example of a style that creates rounded edges for div elements: Yes, I know the other 256 ways to do this with valid CSS ... but this one is very pleasing to the eye. I am interested in any cases where you were faced with a dilemma: best practice / life?
Here I suggest you speculate on the topic Best working practices versus life!
Unit testing for any occasion
A typical case: a mid-level project, the logic is quite simple, you have short iterations.
And you have a low error price, that is, you do not write a banking application where there is a chance to lose millions in the event of an error. It's like this: someone found a mistake, wrote to you, you said thanks and fixed it.
I respect Extreme Programming (XP), but I am not a supporter of TDD [ Test-driven development ] where you first need to create tests that describe the requirements for the code, before writing the code itself, so you need to create a test for each feature.
In my opinion, TDD increases costs without giving corresponding advantages in return (except for projects with a high cost of errors). It seems reasonable to me to find a balance and use Unit tests for critical application logic.
CSS markup
“Friends, how is it that you do not have valid CSS on the pages: ...”
from a letter to our company from a user of the service.
Yes, I love W3C validators [ W3C the validators ] but when confronted with the convenience against W3C validity choose convenience.
An example of a style that creates rounded edges for div elements: Yes, I know the other 256 ways to do this with valid CSS ... but this one is very pleasing to the eye. I am interested in any cases where you were faced with a dilemma: best practice / life?
.rounded-corners {
border-radius: 5px;
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
-o-border-radius: 5px;
-khtml-border-radius: 5px;
}