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*
- 157"Novice developers are prone to overly complex and clever code, because it requires a more experience to be able to see the simplest and clearest solution" can't agree more with you. Excelent answer!Bonifacio– Bonifacio2017-06-06 11:16:05 +00:00Commented Jun 6, 2017 at 11:16
- 24Overly complex code is also quite passive-aggressive. You're deliberately producing code that few others can read or debug easily...which means job security for you, and utter hell for everyone else in your absence. You may as well write your technical documentation entirely in Latin.Ivan– Ivan2017-06-06 20:39:00 +00:00Commented Jun 6, 2017 at 20:39
- 15I don't think clever code is always a show off thing. Sometimes it feels natural, and only looks ridiculous on a second inspection.user69767– user697672017-06-07 07:43:31 +00:00Commented Jun 7, 2017 at 7:43
- 5I have removed the phrasing about "showing off" since it sounded more judgmental than intended.JacquesB– JacquesB2017-06-07 09:17:22 +00:00Commented Jun 7, 2017 at 9:17
- 11@BaileyS - I think that emphasises the importance of code review; what feels natural and straightforward to the coder, especially when gradually developed that way, can easily seem convoluted to a reviewer. The code then doesn't pass review until refactored / rewritten to remove the convolution.Myles– Myles2017-06-08 16:15:45 +00:00Commented Jun 8, 2017 at 16:15
| Show 2 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you