Upgrade StorageDifferences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| dev:how_to_write_a_zotero_translator_2nd_edition:chapter_2 [2010/10/20 23:34] – rmzelle | dev:how_to_write_a_zotero_translator_2nd_edition:chapter_2 [2017/11/12 19:53] – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | < | ||
| + | in the process of updating the documentation for | ||
| + | <a href=" | ||
| + | may be outdated in the meantime. Thanks for your understanding.</ | ||
| + | |||
| + | |||
| ====== Chapter 2: General Troubleshooting Guidelines ====== | ====== Chapter 2: General Troubleshooting Guidelines ====== | ||
| Line 56: | Line 62: | ||
| When fixing problem code, only change one thing at a time. If you are working on a section of code that has several issues, fix one problem and retry the code before moving on. Sometimes if you make three or four changes before retrying the program, you will inadvertently cause another unexpected problem. This can make you think your fix was incorrect, when in fact only the last change you made was wrong. Change one thing and make sure it works before moving on and you will prevent a lot of confusion. | When fixing problem code, only change one thing at a time. If you are working on a section of code that has several issues, fix one problem and retry the code before moving on. Sometimes if you make three or four changes before retrying the program, you will inadvertently cause another unexpected problem. This can make you think your fix was incorrect, when in fact only the last change you made was wrong. Change one thing and make sure it works before moving on and you will prevent a lot of confusion. | ||
| + | |||
| + | **Next**: [[dev/How to Write a Zotero Translator, 2nd Edition/ | ||