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*
-
43Good answer, but maybe you should mention testing. How does one deal with infinite loop in unit test ? Doesn't such loop 'break' the tests ???GameAlchemist– GameAlchemist2016-04-17 09:39:47 +00:00Commented Apr 17, 2016 at 9:39
-
150@GameAlchemist That's the pizza test. If my code doesn't stop running in the time it takes me to make a pizza I start to suspect something is wrong. Sure it's no cure for Alan Turing's halting problem but at least I get a pizza outta the deal.candied_orange– candied_orange2016-04-17 09:52:13 +00:00Commented Apr 17, 2016 at 9:52
-
12@CodeYogi - actually, it can get very close. Start with a test that operates on a single value. Implement the code without a loop. Then write a test that operates on two values. Implement the loop. It is very unlikely you'll get a boundary condition wrong on the loop if you do it like this, because in almost all circumstances either one or the other of these two tests will fail if you make such a mistake.Jules– Jules2016-04-17 18:16:55 +00:00Commented Apr 17, 2016 at 18:16
-
16@CodeYogi Dude all due credit to TDD but Testing >> TDD. Outputting a value can be testing, getting a second set of eyes on your code is testing (you can formalize this as a code review but I often just grab someone for a 5 minute conversation). A test is any chance you give an expression of your intent to fail. Hell you can test your code by talking through an idea with your mom . I've found bugs in my code when staring at the tile in the shower. TDD is an effective formalized discipline that you don't find in every shop. I've never once coded anywhere where people didn't test.candied_orange– candied_orange2016-04-17 18:38:19 +00:00Commented Apr 17, 2016 at 18:38
-
13I was coding and testing years and years before I'd ever heard of TDD. It's only now that I realize the correlation of those years to the years spent coding while wearing no pants.candied_orange– candied_orange2016-04-18 06:44:52 +00:00Commented Apr 18, 2016 at 6:44
|
Show 20 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