Slightly late blog update this week, owing mainly to the amounts of midterms and the thesis progress that had to be made last week. However, we are back and kicking: and I hope that I will be able to keep this momentum up next week as well. In today's newsletter, I would love to highlight some fun code I wrote for my Honors Thesis last semester.
This newsletter is a special one to me: it is the third week that I am writing something down on this platform without fail, and thus building up the momentum to continue doing the same for a longer period of time. The issues that come with scheduling problems, or a general lack of motivation towards doing something start to dwindle by the time it is the third week of committing to a new habit.
(noun) /dɪˌbʌɡzaɪ.əti/
Definition: The apprehensive and uneasy feeling experienced by a programmer when faced with the prospect of executing or testing code, particularly after investing a significant amount of time in its creation, due to the anticipation of potential errors, bugs, or the need for extensive debugging.
Example: Sarah hesitated to run the program she had been tirelessly working on for days, overcome by a wave of debugxiety as she feared encountering unforeseen issues that might demand prolonged debugging sessions.
Etymology: Blend of "debugging" and "anxiety."
While I have gotten this opportunity through an academic source, the contents of this blog do not reflect any of that. This blog is part of my "digital garden": a virtual space to collect raw thoughts as is. This is not a reflection of UMass Amherst, iCons, U.S. Census Dept, The Opportunity Project, and any/every organization mentioned. This space only exists to collect personal thoughts, and is very informal, and not representative of any ideas, thoughts, or emotions behind anything.
Visit the Research Page to learn more on the academic end of this project. That is where I document the crucial, tangible, proper outcomes of this project.