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.
-
-1. Sarcastic and bad analogy, not an answer.Fosco– Fosco2011-12-10 17:42:14 +00:00Commented Dec 10, 2011 at 17:42
-
@Fosco Sarcastic, yes. Bad analogy? Why? It's exactly the same pattern that I've seen far too many times not to feel sarcastic about it. People used to one level of abstraction complaining that the introduction of an higher one is hiding the True Behaviour without remarking that what they take as the True Behaviour is just a level abstraction built over others. The only one I've never seen culprit of it are those making transistor models. They know very well they are building a level of abstraction over something mastered by nobody.AProgrammer– AProgrammer2011-12-10 18:55:12 +00:00Commented Dec 10, 2011 at 18:55
-
It is as common and as irritating as the other pattern, people used to a level of abstraction not wanting to use a lower one because it is too low without remarking that the question isn't "is it an higher or lower level of abstraction" but "is it the most appropriate one".AProgrammer– AProgrammer2011-12-10 19:08:46 +00:00Commented Dec 10, 2011 at 19:08
-
I get your point, but I still have a problem with the analogy and it's not a real answer. The switches on the front panel method no longer exists, so it's not a choice you can make... Some languages really do make things 'magic' and it's very difficult to give up control of the application flow and trust that your framework is going to put all the pieces together properly.Fosco– Fosco2011-12-10 19:20:58 +00:00Commented Dec 10, 2011 at 19:20
-
@Fosco, it always was difficult. I feel obligated to cite the story of Mel. And don't forget my second comment about the use of the right level of abstraction, it sometimes makes sense not to use the highest level available.AProgrammer– AProgrammer2011-12-10 20:00:52 +00:00Commented Dec 10, 2011 at 20:00
|
Show 1 more comment
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
lang-java