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.

I would assert that you never know whether you can trust the data coming in because it's coming in to a function and is a nullable type. Code could be refactored to make the input totally different. So if there's a null possible you always gotta check. So you end up with a system where every variable is checked for null every single time before it's accessed. The cases where it's not checked become the failure percentage for your program.

Chris McCall
– Chris McCall

2015-04-10 18:52:06 +00:00
Commented Apr 10, 2015 at 18:52

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 »