{"id":9,"date":"2023-01-27T03:23:02","date_gmt":"2023-01-27T03:23:02","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/fogg\/?p=9"},"modified":"2023-01-27T03:23:02","modified_gmt":"2023-01-27T03:23:02","slug":"avoiding-and-getting-un-stuck","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/fogg\/2023\/01\/27\/avoiding-and-getting-un-stuck\/","title":{"rendered":"Avoiding and Getting Un-Stuck"},"content":{"rendered":"\n<p>There\u2019s countless approaches to problem solving. A quick search on Google will yield tons of varying results. Each of which have a degree of overlap. However, most of them do not really cover how to handle the situation when you end up stuck. Not \u201cif\u201d you get stuck, but \u201cwhen.\u201d I\u2019m not saying everyone will get stuck on any given problem, but it\u2019s inevitable that you\u2019ll get stuck at some point. Let\u2019s dive into some techniques that I have found helpful to me. Likely some if not all will seem familiar to you.<\/p>\n\n\n\n<p>First and foremost, it\u2019s important to start the process early. This will budget in time into the process if you get stuck and run into a problem. This extra time allows you to try the different techniques; especially the last one that can be extremely helpful if it\u2019s a particularly challenging problem. Starting early is paramount. If you don\u2019t need the time, you can spend it on the back-end instead of the front-end.<\/p>\n\n\n\n<p>For any problem, it\u2019s critical to have notes, a documented approach or outline to refer back to if you run into an issue. This needs to be derived directly from the project requirements. If done properly, you\u2019ll have at very least a logically approach to solve any part of the problem you\u2019re working on if not already solved it on paper. The issue is often lies with the implementation. Either an error in translating the logic to the implementation or a missed logic outright! It\u2019s easier to miss cases. Especially when there are a lot of small ones.<\/p>\n\n\n\n<p>If the problem is more challenging than you thought talking the problem out loud goes a long way. If you\u2019re lucky enough to have someone around to talk to that\u2019s the best case. Even if they don\u2019t have a background in whatever the topic is try break down the logical approach for them. Otherwise, tell a pet or any inanimate object. As long as you\u2019re literally saying it out loud, it can help you self-trigger on something you missed.<\/p>\n\n\n\n<p>Now if you\u2019re really stumped, taking a break is the best thing. No matter your convictions or motivations, take the break. You\u2019ve heard, \u201csquare peg, round hole\u201d. Well right now, your mindset is a square peg and the solution is a round hole. Yes you can eventually cram a solution through. However, taking this break can reframe your mind-set to work towards a solution more efficiently. Often you\u2019ll spend less time overall problem solving utilizing this approach. Even if it seems counterintuitive. By budgeting this time in, you can save yourself a lot of frustration and time.<br><br>They may seem simple, but utilizing these techniques in this sequence can help you work through many problems. Yes, the sequencing was intentional. Take them and try them for yourself. I hope they work for you as they have for me.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There\u2019s countless approaches to problem solving. A quick search on Google will yield tons of varying results. Each of which have a degree of overlap. However, most of them do not really cover how to handle the situation when you end up stuck. Not \u201cif\u201d you get stuck, but \u201cwhen.\u201d I\u2019m not saying everyone will &hellip; <a href=\"https:\/\/blogs.oregonstate.edu\/fogg\/2023\/01\/27\/avoiding-and-getting-un-stuck\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Avoiding and Getting Un-Stuck<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":13203,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-9","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/posts\/9","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/users\/13203"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/comments?post=9"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/posts\/9\/revisions"}],"predecessor-version":[{"id":10,"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/posts\/9\/revisions\/10"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/media?parent=9"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/categories?post=9"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/fogg\/wp-json\/wp\/v2\/tags?post=9"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}