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.
- Do you agree that this is a tradeoff between simplicity and complexity, which ultimately a tradeoff between short-term and long-term? And in projects with short deadlines and tight budgets, or in small businesses that are in the survival stage, then you need to prioritize short-term over long-term? I see that this is the same with using design pattern: start small, and refactor as you grow. Applying them too soon will make them become anti-patternsOoker– Ooker2023-10-08 06:43:05 +00:00Commented Oct 8, 2023 at 6:43
- So my question is not about why the devs get frustrated with short-term people, but why they don't frame the situation as each situation has its own solution, or each tool serves its own need, and too focusing on long-term solutions will not be good for short-term situations?Ooker– Ooker2023-10-08 06:44:38 +00:00Commented Oct 8, 2023 at 6:44
- @Ooker, given that "simplicity" and "complexity" are generally regarded as diametrically opposite qualities, it follows that there must always be a trade off between those two. I'm not sure that each corresponds to short-term and long-term however. Short-termism in development is often characterised by undue complexity on the whole, not by over-simplification. (1/3)Steve– Steve2023-10-08 07:51:24 +00:00Commented Oct 8, 2023 at 7:51
- 1I'm not sure devs get frustrated at single short-term solutions when an emergency demands it, but by management who are insufficiently strategic in thought and who (lacking the slightest understanding) think that everything can be solved with short-term solutions. This is roughly what developers mean by "technical debt" - it's basically work that should be done but hasn't yet been, and therefore leaves the existing situation over-complicated or error-prone. Eventually, the situation becomes unmanageably complex and highly incorrect and prone to dysfunction. (2/3)Steve– Steve2023-10-08 07:56:12 +00:00Commented Oct 8, 2023 at 7:56
- 1@Ooker: wishful thinking, the Dunning-Kruger effect and the Iceberg Secret.Doc Brown– Doc Brown2023-10-08 10:36:48 +00:00Commented Oct 8, 2023 at 10:36
| Show 4 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