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*
- 3+1 Thanks for the insight. "to design if you know know how things work" -> " to design if you don't know how things work" ?tokland– tokland2012-08-01 10:07:46 +00:00Commented Aug 1, 2012 at 10:07
- Hey builder, I suggested some edits to this post, I think you have excellent points, I just tried to clean up some grammar.Steven– Steven2012-08-01 16:28:30 +00:00Commented Aug 1, 2012 at 16:28
- I definitely agree with the point about programming being more of an art than engineering. I often find creativity as a core aspect in software design.Lanzafame– Lanzafame2014-11-25 06:03:00 +00:00Commented Nov 25, 2014 at 6:03
- 1I disagree with the assertion that a large software project and a tower have similar complexity - based on my experience working as both a structural engineer and a software engineer, I'd say software complexity is much higher. There's probably a raft of reasons for this, but the one I'd suggest is that there's a whole lot of wiggle room in engineering; the upper bound of construction design is almost always given by cost, and that's a soft constraint. Software needs to be exact, since computers don't deal with ambiguity well. Slab not working? Add a shitload of steel, she'll be right.Simon Robb– Simon Robb2017-10-07 11:32:13 +00:00Commented Oct 7, 2017 at 11:32
- Some people do design and build buildings for pleasure. Don't tell my employer, but now that I think of it some of my software is like the Sagrada Familia: Idiosyncratic, too many ornaments, never quite finished; but of interesting design, fun to build and use and still standing.Peter - Reinstate Monica– Peter - Reinstate Monica2018-07-16 12:13:23 +00:00Commented Jul 16, 2018 at 12:13
Add a 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