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.
- 2Oh yes, sure. Completely agree. It's just that when you can't get 100% of what you want, you might have to settle for less. You know that less is not so good but it is better than nothing.quickly_now– quickly_now2011-08-20 08:23:31 +00:00Commented Aug 20, 2011 at 8:23
- 4I generally agree with cross-testing but on some teams that'll introduce conflicts. Some people enjoy blaming others ("my stuff works, yours not, lol, I'm so much better than you") and that is unacceptable. I've witnessed that numerous times. Crosstesting should only be done between colleagues who respect each other. On my team I've introduced the nameless developer who is blamed for every bug to avoid that anyone loses his/her face. Bugs are nameless, they happen.Falcon– Falcon2011-08-20 10:47:03 +00:00Commented Aug 20, 2011 at 10:47
- 5+1 it is impossible to properly test your own code. It is amazing which tricks the mind can play on you - you'll be 100% sure you coded and tested some function and it will take somebody else to show to you it's actually doesn't work except in very narrow case and it'd be obvious for you once shown - but you would never see it yourself. The mind uses cognitive shortcuts, and in testing those make impossible for the person who designed and developed the code to properly test it.StasM– StasM2011-08-21 00:02:47 +00:00Commented Aug 21, 2011 at 0:02
- 2@StasM - agreed, with one small qualification: I have found that coming back to my own code months later, I can see the faults and can do a better job of testing it objectively. But test your own after writing is very hard indeed.quickly_now– quickly_now2011-08-21 01:34:47 +00:00Commented Aug 21, 2011 at 1:34
- 1@Ben Aston: A developer should still be doing unit tests, integration tests, etc. Just not exclusively. The blind spots won't go away just because you want them to.quickly_now– quickly_now2011-08-21 23:15:23 +00:00Commented Aug 21, 2011 at 23:15
| Show 3 more comments
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