{"id":10,"date":"2025-01-16T18:50:56","date_gmt":"2025-01-16T18:50:56","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/kylefree33\/?p=10"},"modified":"2025-01-16T18:50:56","modified_gmt":"2025-01-16T18:50:56","slug":"cs462-blog-post-1","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/kylefree33\/2025\/01\/16\/cs462-blog-post-1\/","title":{"rendered":"CS462 Blog Post #1"},"content":{"rendered":"\n<p>Looking back at my old code is something I like to do fairly often, it is encouraging and shows me how far I&#8217;ve come. It is also good to be reminded of the projects I have worked on in the past. There have definitely been points where I could not understand it, but it happens less often than I would think. The biggest\/most important thing I&#8217;ve learned about good code and good comments is you don&#8217;t put what the code does in the comment, you put the reasoning for why the code is there to begin with. This has helped me tremendously. As for bad practices, I think the worst of all is when a code base forever grows in complexity, especially when teams are working on it. I often see that instead of taking time to re-do code that is no longer serving a team, it is often just expanded or split into another branch of logic that then also needs to be updated every single time once there is a change. This happens at work where there are multiple Jenkins files, because there was a point where the versioning was causing issues, and now once something is changed it needs to be updated in 4 different places and is always a headache. Which could have all been solved by taking a few extra minutes to refactor and simplify the original code.<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Looking back at my old code is something I like to do fairly often, it is encouraging and shows me how far I&#8217;ve come. It is also good to be reminded of the projects I have worked on in the past. There have definitely been points where I could not understand it, but it happens [&hellip;]<\/p>\n","protected":false},"author":14596,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/posts\/10","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/users\/14596"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/comments?post=10"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/posts\/10\/revisions"}],"predecessor-version":[{"id":11,"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/posts\/10\/revisions\/11"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/media?parent=10"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/categories?post=10"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/kylefree33\/wp-json\/wp\/v2\/tags?post=10"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}