{"id":18,"date":"2021-10-21T13:44:51","date_gmt":"2021-10-21T13:44:51","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/heymae\/?p=18"},"modified":"2021-10-22T02:24:45","modified_gmt":"2021-10-22T02:24:45","slug":"sometimes-you-just-have-to-set-things-on-fire-metaphorically","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/heymae\/2021\/10\/21\/sometimes-you-just-have-to-set-things-on-fire-metaphorically\/","title":{"rendered":"Sometimes you just have to set things on fire (metaphorically)"},"content":{"rendered":"\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/osu-wams-blogs-uploads.s3.amazonaws.com\/blogs.dir\/4726\/files\/2021\/10\/burn-elmo.gif\" alt=\"\" class=\"wp-image-21\" width=\"287\" height=\"195\" \/><\/figure>\n\n\n\n<p>I&#8217;ve always been a bit stubborn, in that I like to believe that with a bit of hard work and elbow grease, almost every problem can be solved. Last week, I ran into a bit of a blocker with Android studio and would like to share my experience along with some lessons learned:<\/p>\n\n\n\n<p>As a student, I haven&#8217;t had the most experience with &#8220;new&#8221; languages, and generally speaking, upgrading an IDE that I&#8217;m using has been more or a leisurely stroll down the beach (I&#8217;ll do it if I remember) than ASAP PANTS ON FIRE.<\/p>\n\n\n\n<p>Thus, I was kind of taken aback when I ran into issues after creating my project in a slightly older version of Android studio that I had previously installed on my computer. Initially, my project seemed fine and I could get the initial &#8220;hello world&#8221; screen up and running. As I was working on installing some external packages, I ran into issues with my Kotlin version. I tried just installing the Kotlin plugin version from the Jetbrains website, however, I had no luck actually loading it into android studio. Total dead end. I realized I had to upgrade my IDE and then upgrade the Kotlin version. While upgrading, I ran into issues while my android studio tried to piece itself together, in its newer and (supposedly) sleeker form. I wasted a bunch of time retrying to upgrade individual parts that were failing and ultimately ended up deleting android studio and installing the new version from scratch. Once I finally had a new version, I had to make a bunch of changes in my project build files to get it up and running.<\/p>\n\n\n\n<p>This lesson was somewhat painful and ended up being the culmination of several days of work, but now with a much clearer head, I can reflect on the experience and hopefully remember these takeaways the next time I&#8217;m in a similar situation:<\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Error messages are your friend<\/li><li>Sometimes you have to just run things and see what happens<\/li><li>It&#8217;s good to try to fix something, but occasionally you will run into an issue where the solution is much more painful than just starting from scratch. It&#8217;s ok to toss in the towel, especially if you end up in the same exact spot. (Note: This doesn&#8217;t mean you should erase your coworker&#8217;s or legacy code because you don&#8217;t understand it)<br><\/li><\/ol>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve always been a bit stubborn, in that I like to believe that with a bit of hard work and elbow grease, almost every problem can be solved. Last week, I ran into a bit of a blocker with Android studio and would like to share my experience along with some lessons learned: As a &hellip; <a href=\"https:\/\/blogs.oregonstate.edu\/heymae\/2021\/10\/21\/sometimes-you-just-have-to-set-things-on-fire-metaphorically\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Sometimes you just have to set things on fire (metaphorically)&#8221;<\/span><\/a><\/p>\n","protected":false},"author":11566,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-18","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/posts\/18","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/users\/11566"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/comments?post=18"}],"version-history":[{"count":3,"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/posts\/18\/revisions"}],"predecessor-version":[{"id":22,"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/posts\/18\/revisions\/22"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/media?parent=18"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/categories?post=18"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/heymae\/wp-json\/wp\/v2\/tags?post=18"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}