Text entry answers for sorted by frequency of occurrance.
(9) | Maintainability |
(5) | Readability |
(3) | CListCtrl |
(2) | ease of maintenance |
(2) | Readability of the code |
(2) | Stability -- less risky code |
(1) | Structure and readability of code |
(1) | suicide rate |
(1) | USER PROOFING ! ! ! |
(1) | Whatever is especially relevant to the particular application and its user(s). |
(1) | Whatever is needed after it is written |
(1) | Readability/Maintainability |
(1) | Reduce Working Set |
(1) | reliability |
(1) | Reusability, Interoperability,... |
(1) | reuse |
(1) | re-useability and maintenance |
(1) | Securety |
(1) | Size of program |
(1) | source code |
(1) | Speed of any code that can be sped up easily |
(1) | Maintainability and extensibility |
(1) | maintainability of code |
(1) | maintainability of the code |
(1) | Maintainanbility |
(1) | Maintanability |
(1) | maintenance |
(1) | Maintenance / Edit-ability |
(1) | mantainability |
(1) | Error handling |
(1) | Evolvability |
(1) | Features |
(1) | Flexibility |
(1) | |
(1) | I just write proper code |
(1) | It depends on the constraints of each project |
(1) | Look and feel |
(1) | Maintability |
(1) | Code simplicity and correctness |
(1) | CPianoCtrl |
(1) | Defensive Coding |
(1) | Depends on what is important to each project: sometimes minimal memory usage is important; somtimes it's responsivenes. Sometimes development cost is what has to be minimised, so no code opimisation. |
(1) | 1234 |
(1) | 66812 |
(1) | abc |
(1) | Awesomeness |
(1) | CfuckingListCtrl is no longer funny. |
(1) | clear code |