| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 7 months |
| seen | Mar 4 at 20:17 | |
| stats | profile views | 38 |
|
Dec 6 |
comment |
Does simplicity always improve Readability? "Coding styles and standards" was the name of the document. Obviously this isn't a standard (as in "Never use GoTo" or "Never use short ints") but a style. Unifying style is important to readability and maintainability. |
|
Dec 6 |
comment |
Does simplicity always improve Readability? What I like most about this answer (and why I accepted it) was because of the definition of simplicity. It helps me see that simplicity can be either more abstract or more concrete. My line of thinking in regards to simplicity wasn't well formed and this has helped a lot. |
|
Dec 6 |
awarded | Scholar |
|
Dec 6 |
accepted | Does simplicity always improve Readability? |
|
Dec 6 |
awarded | Nice Question |
|
Dec 5 |
comment |
Does simplicity always improve Readability? +1 for the quote, but does simplicity improve readability? |
|
Dec 5 |
comment |
Does simplicity always improve Readability? That was the goal that I aimed for and that was the stated object. Simplicity (or rather, the one function/operation per line) seemed to naturally follow from that goal. I'm trying to ascertain whether my understanding was invalid. When you're building a coding standards, establishing a set of rules and guidelines is the entire point of the exercise. Setting rules and guidelines that are too vague is useless. As such, this answer really doesn't help. |
|
Dec 5 |
awarded | Student |
|
Dec 5 |
asked | Does simplicity always improve Readability? |
|
Dec 1 |
comment |
How can I deal with the cargo-cult programming attitude? Really? If an instructor isn't helpful enough to help the student get their code working, are they really doing their job? |
|
Nov 30 |
awarded | Teacher |
|
Nov 30 |
answered | How can I deal with the cargo-cult programming attitude? |
|
Nov 3 |
awarded | Citizen Patrol |
|
Oct 18 |
awarded | Supporter |