Today marked a pivotal point in my internship journey. A hastily scheduled meeting with my mentor and the intern coordinator brought a renewed clarity to my project, and I can't help but reflect on how valuable these moments of introspection can be. The meeting was supposed to be a routine check-in, an opportunity for each intern to discuss their project's progress. However, I found myself stumbling over my words when asked to delve into the specifics of my project. It suddenly dawned on me that I had allowed myself to become slightly disconnected from the core essence of what I was working on. As someone who isn't deeply versed in electronics, the technical intricacies often felt overwhelming, leading me to focus more on the coding aspect. But it was during this meeting that a critical realization hit me like a bolt of lightning. While I had been meticulously checking for syntax errors and gaining the Electrical Engineer's approval, I had neglected a fundamental step in the coding process: thorough testing. Testing, the very mechanism through which we debug and validate our code, had somehow slipped my mind. The meeting clarified this blind spot and highlighted the importance of testing. My mentor rightly pointed out that the purpose of learning to run multiple files in Python was precisely for this reason: to test the code comprehensively. I had been inadvertently undermining the integrity of my work by not conducting proper tests. It's like constructing a building without ensuring each brick is solidly in place. Buoyed by this epiphany, I embarked on a journey of testing my code in earnest. I put my newfound knowledge to work, dissecting my code and meticulously running test cases for each component. I was amazed at how quickly I was able to identify and fix errors that had previously eluded me. The code started to flow seamlessly, and I could sense a newfound synergy between my coding skills and the project's intricate electronics. As I navigated through the testing process, I also received a clarifying conversation from a mentor who was not an Electrical Engineer. Though I must confess that the specifics of the wifi-adc component's functionality slipped through the cracks of my memory, I was quick to realize the importance of documenting every piece of advice I receive. I promptly requested my mentor to pen down the details, ensuring I have a comprehensive reference for future endeavors. Today's experience has taught me that sometimes, we need to step back, reflect, and recalibrate our approach.