![\"Woman](\"https:\/\/i0.wp.com\/wowfall2020.londietmartin.com\/wp-content\/uploads\/2020\/10\/pexels-andrea-piacquadio-3755761-1.jpg?resize=512%2C341&ssl=1\")
<\/figure><\/div>\n\n\n\nCoding is no different than cooking up dinner for the holidays, organizing and categorizing your pantry to losing weight and running a marathon. All these tasks may seem too big and complex to take on. However, once you begin to break the problem down into steps, it gets easier and less tedious to solve. It is all about building a system that is functional and maintainable for you.<\/p>\n\n\n\n
In the coding world, we call this incremental development which intends to avoid debugging by adding and testing only a small amount of code at a time (<\/a><\/strong>1<\/sub>). <\/strong>Unsurprisingly, the more lines of code you write, the more lines of code you will need to debug. Therefore, its important to write, test and execute. So, from experience, I would make this a habit. It is easy to get defeated when your code is not working or behaving properly. However, errors in your code allow you to see its flaws. It is better to catch them now, before someone else does.<\/p>\n\n\n\n There are different types of errors that you may come across with buggy code. Identifying the source can save you time and confusion. They normally fall into the following three categories.<\/p>\n\n\n\n These are errors that occur when you violate the rules of writing in that specific language. <\/strong>This compiler error indicates something that must be fixed before the code can be compiled (<\/strong>2<\/sub>).<\/strong> These are the most common errors that beginners see first like a missing semicolon or bracket.<\/p>\n\n\n\n Errors which occur during program execution after successful compilation (<\/strong>2<\/sub>). <\/em><\/strong>Starting out, I would not stress over this. Your programs will be simple enough where you will not run into this issue just yet.<\/p>\n\n\n\n This error occurs when the statements written in the program are not meaningful to the compiler (<\/strong>2<\/sub>)<\/strong>. <\/em>Therefore, this is more difficult to see. So, as a programmer, you must make a mental note of what the code should intentionally be doing.<\/p>\n\n\n\n For beginners, it\u2019s hard to pinpoint where the errors are coming from. The error might not be happening on the line that your developer tool is suggesting. It could be occurring in the code above you. For instance, you could have mistyped or forgot to add proper headings to your document.<\/p>\n\n\n\n Are you experiencing problems in the code below? Did you forget to add a return statement or a closing tag? Whichever one may be the case, it is important to separate the code out into sections. You should always divide and conquer.<\/p>\n\n\n\n If I know that I have gotten ahead of myself, I like to start over. It gives me a clean slate to think about my code and refocus. Although, you should always save the code previously worked on somewhere else. So, if you must go back to it, you will have it.<\/p>\n\n\n\n Coding requires a great deal of precision and patience. Yes, you wrote the same code for the thousandth time. However, you are not immune from the same errors occurring for the thousandth time. Your mind could be focused on the next line of code, errands you need to run, or what you want for lunch.<\/p>\n\n\n\n Its okay to take a break and step away from the computer. Sometimes, its easy to experience programmer burnout. Remember, programming is not a sprint, but a marathon. Work at your own pace and you will get there.<\/p>\n\n\n\n Do not beat yourself up if you do not know what is wrong with your code. Its fine to look things up. Always consider that you are probably not the first programmer to have this issue.<\/p>\n\n\n\n With code, there are multiple ways to solve a problem. I know how easy it is to get caught up solving a problem a certain way. It can be difficult to let go of your original code and implement another solution. However, it is important to explore your options. This is how you make progress and strengthen your skills.<\/p>\n\n\n\n Following programming conventions has made debugging code more efficient for developers. This could be creating separate files, adding classes, indenting space to using identifiers like id tags to variables and functions. Separating and defining your code allows for code reuse. You can fix buggy code for multiple files without going line by line.<\/p>\n\n\n\n (1) Downey, Allen B., Think Python. O\u2019Reilly Media Inc., 2016. <\/p>\n\n\n\n (2) \u201cErrors in C++\u201d, Geeks for Geeks, https:\/\/www<\/a>.<\/a>geeksforgeeks.org\/errors-in-cc\/<\/a> Accessed 5 October 2020.<\/p>\n\n\n\n Source: Images<\/strong><\/p>\n\n\n\n Pixabay. \u201cTurned-on Computer Monitor Displaying Text.\u201d https:\/\/www.pexels.com\/<\/a>. 2016 December 23. https:\/\/www.pexels.com\/photo\/business-code-coding-computer-270360\/<\/a>. Accessed 10 October 2020.<\/p>\n","protected":false},"excerpt":{"rendered":" By: Charlessia Robinson, October 2020 Coding is 10% working and 90% thinking. Truthfully, it can be 90% understanding why the code is not working. In…<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-33","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=\/wp\/v2\/posts\/33","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=33"}],"version-history":[{"count":5,"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=\/wp\/v2\/posts\/33\/revisions"}],"predecessor-version":[{"id":634,"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=\/wp\/v2\/posts\/33\/revisions\/634"}],"wp:attachment":[{"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=33"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=33"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wowfall2020.londietmartin.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=33"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Syntax errors<\/u><\/strong><\/h5>\n\n\n\n
Runtime errors<\/u><\/strong><\/h5>\n\n\n\n
Semantic errors<\/u><\/strong><\/h5>\n\n\n\n
Tips for Debugging<\/span><\/h4>\n\n\n\n
Look behind you<\/u><\/em><\/strong><\/h5>\n\n\n\n
Look in front of you<\/u><\/em><\/strong><\/h5>\n\n\n\n
Undo and start over<\/u><\/em><\/strong><\/h5>\n\n\n\n
Write and test line by line<\/u><\/em><\/strong><\/h5>\n\n\n\n
Take a deep breath<\/u><\/em><\/strong><\/h5>\n\n\n\n
![\"Woman](\"https:\/\/i0.wp.com\/wowfall2020.londietmartin.com\/wp-content\/uploads\/2020\/10\/pexels-mentatdgt-937453.jpg?resize=480%2C320&ssl=1\")
<\/figure><\/div>\n\n\n\nTake time to refresh your memory<\/u><\/em><\/strong><\/h5>\n\n\n\n
Do not get too attached to your code<\/u><\/em><\/strong><\/h5>\n\n\n\n
Follow coding conventions<\/u><\/em><\/strong><\/h5>\n\n\n\n
![\"A](\"https:\/\/i0.wp.com\/wowfall2020.londietmartin.com\/wp-content\/uploads\/2020\/10\/pexels-pixabay-270360.jpg?resize=480%2C320&ssl=1\")
<\/figure><\/div>\n\n\n\n