Day 3: Debugging Disasters

Today was a mix of cloud storage debugging, language learning, and problem-solving. Every task came with its own challenges, but figuring things out was worth it.

---

DocSecure: Cloud Storage and Debugging

We explored Google Cloud Storage for secure document handling, using Node.js and the fetch API to manage file uploads. Debugging turned into a deep dive as we ran into:

• Module errors (get-intrinsic, semver)

• Cloud Bucket permission issues

• API request failures

To fix these, we relied on Copilot by Git, DevTools logs, Node.js version checks, and dependency updates. Since Google Cloud Storage had some access restrictions, we also looked into alternatives like Google Drive API, Firestore, and RAM storage to see what best fits our use case.

---

Duolingo: Keeping the Streak Alive

Despite the heavy debugging, I made sure to keep up with Japanese practice. Focused on sentence structure and learning new kanji.(Mizu / sui: It is a single kanji with different readings as per the word and the way it is used in. It means water. When used individually, we read it as mizu. But for Wednesday, the Suiyoubi word is used. Here, sui means the water element, and youbi means day. *Fun Fact: In the Japanese language, each day of the week is connected with a natural element Fire, water, wood, etc ).

---

LeetCode: Debugging in Coding Too

Solved a LeetCode problem today, which was about checking if a number is a power of two. Solved another small and easy problem as I was quite invested in DocSecure. The bitwise approach using n & (n - 1) == 0 was an interesting trick—leaning more into optimization rather than brute force solutions. I started with the usual brute-force method and used the loop logic but I also learnt about the bitwise approach which was the top solution. (Took less time)

Takeaways from the Day

A challenging but productive day. On to the next!