Yes, those arguments have egos involved. They should put aside their emotions and do what's best for the maintainers of that code and consumers of that code.
-
-
-
@KentBeck once said: if a code quality argument lasts more than 5 minutes then flip a coin. - Još 4 druga odgovora
Novi razgovor -
-
-
Or you're in a group with different taste. I have a recent example. Person entity has integer age but no boolean isAdult. Group member prefer AgeUtil#isAdult(Person p), instead of Person#isAdult(). Last much longer than 5 minutes and one party gave up.
-
Age is wrong modeling. Birthday and today's date or another reference date determines the age. Next year the software should work too?
- Još 1 odgovor
Novi razgovor -
-
-
This, I have come to realize, is true.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
A coworker once made an interesting point about code quality: “when was the last time you said, ‘wow, this is really good code’?”
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Agreed. The only viable yardstick for measuring code quality is the cost of changing that code.
-
Someone I know said the only measure of code quality is “the number of WTFs in a code review” :)
Kraj razgovora
Novi razgovor -
-
-
In a male dominated industry most arguments are ballgames.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Please define quality
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.