{"id":45,"date":"2024-03-05T18:10:31","date_gmt":"2024-03-05T18:10:31","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/bournm\/?p=45"},"modified":"2024-03-05T18:10:31","modified_gmt":"2024-03-05T18:10:31","slug":"the-final-stretch","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/bournm\/2024\/03\/05\/the-final-stretch\/","title":{"rendered":"The Final Stretch"},"content":{"rendered":"\n

As we enter the last couple weeks of the semester, I came to realize several important lessons throughout the development stages of our senior capstone project. Our team is building an AI-powered web tool called MatchIQ which is meant to help jobseekers through features such as smart job searches, resume enhancement, career path support, company culture matching, application tracking, and more. <\/p>\n\n\n\n

What are 5 things you learned from working on your project?<\/strong><\/p>\n\n\n\n

    \n
  1. Know what tasks others have<\/strong> – This may sound like a no brainer but project management softwares like Jira are powerful tools for software development processes. It’s absolutely pertinent that we assign ourselves to a ticket and understand what work others are doing. There were a couple times where there was overlap or someone already completed the work of another. Something as simple as having a name assigned to a ticket can prevent a weeks worth of duplicate work and help ensure we are all on the same page.<\/li>\n\n\n\n
  2. Start Early<\/strong> – It may seem like a week is a lot of time to complete a task. However, we never know when technical issues can arise which hinder our ability to actually work on the task at hand. It’s best to start early in the week in case some software isn’t working or there is a bug. That way if that takes a couple days, we still have the rest of the week to complete our actual work. I’ve realized that projects tend to work as 80% troubleshooting and 20% actual coding.<\/li>\n\n\n\n
  3. Containerize your project<\/strong> – Having everyone on different operating systems and software versions made development a nightmare, as small inconsistencies would cause major bugs. Using containerization helped normalize our environments to avoid issues stemming from discrepancies in our individual setups. <\/li>\n\n\n\n
  4. Ask questions <\/strong>– Being on a team , we all have diverse backgrounds and experiences. When I got stuck, I sometimes wasted hours trying to solve problems alone. Now I know to reach out to teammates right away to get issues resolved more efficiently. Collaborating is so much better than banging my head against the wall!<\/li>\n\n\n\n
  5. Conduct Thorough PR Reviews<\/strong> – Even when swamped with my own tasks, I’ve learned to thoroughly review all code submissions before merging. Once, an overlooked error in a peer’s change broke my copy of the codebase. Now I understand the importance of fully testing all changes to catch bugs before they impact others or merge to main.<\/li>\n<\/ol>\n\n\n\n

    Overall, working on this project reinforced for me that team software development is as much about collaboration as it is coding. Building the product itself requires a joint technical effort, but it’s also a process of coordination, knowledge sharing, and tackling issues together. From being proactive in the teams channel, to assigning our names to a ticket – every step of the way counts. <\/p>\n","protected":false},"excerpt":{"rendered":"

    As we enter the last couple weeks of the semester, I came to realize several important lessons throughout the development stages of our senior capstone project. Our team is building an AI-powered web tool called MatchIQ which is meant to help jobseekers through features such as smart job searches, resume enhancement, career path support, company … Continue reading The Final Stretch<\/span><\/a><\/p>\n","protected":false},"author":13692,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-45","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/posts\/45","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/users\/13692"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/comments?post=45"}],"version-history":[{"count":1,"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"predecessor-version":[{"id":46,"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/posts\/45\/revisions\/46"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/bournm\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}