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.

What worries me is that, if I have testing with proper case coverage, this gives leeway to write code that is poorly written knowing that the testing will catch anything. Right now I'm trying to write code that I am highly certain works, and then have a safety net of test cases.

Janarth K
– Janarth K

2017-02-14 16:05:19 +00:00
Commented Feb 14, 2017 at 16:05
@JanarthK well, of course you decide how you write your own code, but be advised that the worldwide trend, among the vast majority of professional software developers, is with testing. Even for many of us who started programming before testing was even a thing, once we started using it, we started loving it so much, that we are never looking back. Testing is not regarded as an additional safety measure; testing is regarded as the fundamental guarantee of correctness.

Mike Nakis
– Mike Nakis

2017-02-14 16:13:04 +00:00
Commented Feb 14, 2017 at 16:13

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 »