I set out with the goal of cracking the code (pun intended) on getting my program to cooperate with the command prompt, but after what felt like a battle of wits, I had to admit defeat. Sometimes, taking a step back is the best strategy. So, today was my "reset" day. I decided to shift my focus and dive headfirst into understanding big O notation better. It's like learning the secret language of efficiency in the coding world. I started by memorizing the order of big O values from most efficient to least efficient. It's like having a roadmap to optimize your code's performance. Armed with this new knowledge, I decided to put it to the test by tackling a few more LeetCode problems. But let's be real, no one's an island in the coding universe. When I hit a roadblock, I turned to my trusty ally: YouTube. I found tutorials that explained the algorithms I needed to conquer those tricky problems. Sometimes, a fresh perspective and a different explanation can make all the difference. And then, it happened. A moment I've been waiting for. A moment that felt like a personal victory. Today, for the first time ever, I solved a hard difficulty problem entirely on my own. The rush of pride and accomplishment was electrifying. It's like a lightbulb flickered to life in my mind – a testament to the progress I've made and the skills I'm honing. As the day came to a close, I shifted my focus back to the internship project. I reached out to the Electrical Engineer, the sage of our project, to sync up and clarify the behavior the command prompt should exhibit. It's all about ensuring we're on the same page and marching toward a shared vision. So, there you have it. A day of twists, turns, and ultimately, triumphs. As I reflect on the journey from wrestling with the command prompt to conquering coding challenges, I'm reminded that in the world of programming, every obstacle is a chance to learn, adapt, and emerge stronger.