Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 7
    +1 for "simple, elegant, and wrong": I've seen a few of those! However I'd say Readability far outweighs Succinctness. Commented Aug 2, 2011 at 16:29
  • 17
    My only concern is with succinct. To many developers think that Code Golf is good programming. It is not. A single line with one object and 15 method calls is confusing and hard to read or follow. Commented Aug 2, 2011 at 16:32
  • 2
    I don't think he meant to define it as "less lines", that was just an example. Obviously something that is squished into a single line (when it shouldn't be) isn't succinct Commented Aug 2, 2011 at 17:43
  • 1
    I love the phrase prematurely pessimized! Commented Aug 2, 2011 at 18:14
  • 1
    @Chad (and IAbstract) - in my experience it's a difficult and precarious balance between succinct and readable. I would put them equal because readability can depend on the ability level of the person reading the code, which means that sometimes there may be a more "readable" solution for that particular level which is strictly less elegant overall than a more succinct solution that requires more in-depth knowledge of the language or platform. Commented Aug 3, 2011 at 7:31