{"id":16,"date":"2023-01-27T07:56:08","date_gmt":"2023-01-27T07:56:08","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/ledbetni\/?p=16"},"modified":"2023-01-27T07:56:08","modified_gmt":"2023-01-27T07:56:08","slug":"code-smells","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/ledbetni\/2023\/01\/27\/code-smells\/","title":{"rendered":"Code Smells"},"content":{"rendered":"\n<p>Prompt: What is one thing from the articles that you would like to start doing (more often), and why? What is one thing you want to avoid doing and why?<\/p>\n\n\n\n<p><a href=\"https:\/\/www.techtarget.com\/searchsoftwarequality\/tip\/Understanding-code-smells-and-how-refactoring-can-help\">https:\/\/www.techtarget.com\/searchsoftwarequality\/tip\/Understanding-code-smells-and-how-refactoring-can-help<\/a><\/p>\n\n\n\n<p>Refactoring code to remove code smells and sloppy code is a very important part of software engineering. In my experience as a growing engineer, my favorite example of this ideology is abstracting duplicate code into their own functions. Instead of writing code multiple times, it can be very helpful to create a function which may be called with a single line of code. Not only does this look subjectively cleaner, it also makes a codebase substantially more readable. Using clear variable names and function names can turn a sloppy, unreadable codebase into an aesthetically pleasing and readable codebase. <br><br>My goal as a growing developer is to abstract as much repeatable code into separate functions as I can, and avoid muddying up my codebase.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Prompt: What is one thing from the articles that you would like to start doing (more often), and why? What is one thing you want to avoid doing and why? https:\/\/www.techtarget.com\/searchsoftwarequality\/tip\/Understanding-code-smells-and-how-refactoring-can-help Refactoring code to remove code smells and sloppy code is a very important part of software engineering. In my experience as a growing engineer, [&hellip;]<\/p>\n","protected":false},"author":13003,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-16","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/posts\/16","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/users\/13003"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/comments?post=16"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/posts\/16\/revisions"}],"predecessor-version":[{"id":17,"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/posts\/16\/revisions\/17"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/media?parent=16"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/categories?post=16"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/ledbetni\/wp-json\/wp\/v2\/tags?post=16"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}