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.

7

Yet anotehr -1 for worring about performance over readablity, maintainablity bla bla bla. Performance is not a reason.

mattnz
– mattnz

2012-03-11 04:41:25 +00:00
Commented Mar 11, 2012 at 4:41
May I know why are you running around distributing -1s without explaining? Defensive programming means more lines of code, that means poorer performance. Anybody care to explain before shoting down the score?

Manoj
– Manoj

2012-03-11 16:23:48 +00:00
Commented Mar 11, 2012 at 16:23
3

@Manoj: Unless you've measured with a profiler and found a block of code to be unacceptably slow, code for readability and maintainability far before performance.

Daenyth
– Daenyth

2012-03-11 17:28:59 +00:00
Commented Mar 11, 2012 at 17:28
What @Manoj said with the addition that less code universially means less to work on when debugging and maintaining. The hit on developer time for anything less that perfect code is extremely high. I am assuming (like me) you don't write perfect code, forgive me if I am wrong.

mattnz
– mattnz

2012-03-11 19:08:45 +00:00
Commented Mar 11, 2012 at 19:08
2

Thanks for the link - Interesting read that I have to agree with it, to a point... Working on a life critical systems, as I do "The system printed the stack trace, so we know exactly why those 300 people died needlessly....." isn't really going to go down too well in the witness stand. I suppose it's one of those things where every situation has a different appropriate response.

mattnz
– mattnz

2012-03-12 02:30:59 +00:00
Commented Mar 12, 2012 at 2:30

| Show 6 more comments

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 »