Last day of REU! On Wednesday and Thursday, I spent time finishing formatting our protocol in LaText with Overleaf, cleaning and uploading my code to Git, and cleaning my desktop for future users. I also attended workshops on grad school application and industry job search, as well as the Stauffer Series on the commonality of Shakespeare and Python.
Today, I prepared for our final REU in Data Science presentation, went to a final CS/DS lunch, did a team debrief of the REU program, and presented for the last time! In addition, I improved my resident contact script so that Green Crew could edit the e-mail/text content more easily through Google Docs. I added a testing sheet and function so that it would be easier for Kanami to edit the content and test-run it on herself.
This summer was a summer of learning, fun, and coding experience for me! I especially loved all the workshops and lectures, where I heard talks ranging from machine learning to operations research! I know that I am taking back transferrable skills such as problem solving, presentation, and teamwork, and I really enjoyed the experience of doing community outreach and applying technology to social justice issues.
(8/1~8/2) Of course, you are never done with debugging/developing! I was in contact with Kanami, because she was running into some errors with the contact tool. I couldn’t find any error with my code, so I looked through her Google Sheets, and found that there were some issues with the content (missing resident name, values in the wrong columns). Hence, the e-mail was not sent for the rows following the first error discovered.
While I would like to make error messages easier to Kanami to understand and fix herself, that would take a longer time to develop. So what I did was make it easier for her to revisit her problems by adding two new menus, resendEmail and resentText that will allow Green Crew to resend e-mail or text for a desired row range that they enter. It also allows them to choose which content they want to send (weekly/custom). This will prove useful in case a function failed due to some error in the content and some residents did not get the message.
It’s exciting to have my tool put into real world application, because now I get to see what additional features would be nice to have, and some problem areas the user runs into!