I'm stuck with many reactions to questions that show that as a result of developers their code Meaning I knight-peak about postfix / prefix enhancement, because I used to use a boolean with two values, and about the proper function naming, and ... to use the boolean Nick-picking
The question is more important: when permission is given to ignore any words that are written? Where is the borderline?
- operator ++ (postfix / prefix)
- string.empty () versus string == ""
- vector.empty () vs vector .size () == 0
- Tell the truth on {on, off} versus bullion; Close = false
- ...
Name it
Edit -
I did not mean (Micro ) -Question about the need for a protest. Instead, I want the opinion that how well you are aware what you are writing, and on the statements like "But it is ready for a dwarf, anyway, let me give it an enum Why should you make it? " (This is an extreme case ...).
I very That's not a lot of people, but there are so many codes during that time, I have learned a thing which has been proved by the right time and time again: when you get muddy, when you ignore the details, Em> Creeps in flaws
Defect cost time and money to repair You can either spend time writing the code cleanly and clearly, if it is cheap to do so, or after you You can spend a lot of time and money chasing a fault in code, which you do not remember well because you slap it in a hurry or because it does not conform to the coding, the end result is, You can spend time and money Are after. In addition, you are wasting time and money which you do not want to waste to start, because it could have stopped a little bit in advance in the investment.
I have never regretted being careful about the way I am writing the code. It has never come to come back to me, being sloppy, I had to come back forever.
Comments
Post a Comment