Edit - Software Engineering Stack Exchange

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*

Rev

Isn't the fact that most sw developers can get by without knowing the inner workings of the system a strong indicator of extensive reuse? I also find it funny how government project stories get out that sound simply dreadful but if you had any knowledge about government work then you would understand how clueless the author is. The $1500 hammers etc... All become understandable when you recognize that government processes required 10 people to review and get competitive quotes before purchase OR it was simply not moving funds between accounting buckets.

Dunk
– Dunk

2013-07-22 15:21:42 +00:00
Commented Jul 22, 2013 at 15:21
I take no comfort in knowing that a software engineer who works on "the most complex" computer system in an aircraft has not slept in 32 hours. =)

RubberDuck
– RubberDuck

2015-05-01 22:19:19 +00:00
Commented May 1, 2015 at 22:19

Add a comment |

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

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>

formatting help »
answering help »