I have decided that writing this newsletter every week was resulting in a content churn, which was essentially me writing a blog post for the sake of writing it. Hence, I am putting down some changes as to how I write this thing: i.e. I would write whenever I have quite a lot to say (in a meaningful way), while also making it such that I write at least once every month.
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.
I often like to mention how my career today started off as a childhood dream. While this is not false, coming here meant giving up on a different dream.
I had always been passionate about music & art, and specifically creating it. However, I was never able to afford the equipment required to pursue this passion. As a result, my primary form of expressing artistic creativity went towards Code.
(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."