Log into Canvas on my phone—laptop’s in the shop, and the assignment is due tomorrow morning. Not ideal, but I’ve got to attempt it anyway. Click the link to Brace Tools, and thankfully, I’m already logged in. Brace greets me in my native language, which is a nice touch, especially since I’m feeling stressed about doing this on a tiny screen. Admit: "I didn’t do the reading, lol." Brace reassures me—this isn’t just a quiz, it’s a learning opportunity. That’s a relief. First code snippet comes up, but it’s hard to read the details on my phone. I ask Brace, "Can you give me some options to choose from?" Brace lists a few refactoring methods from Fowler’s book—clear and concise. I tap on "Extract Method" after a bit of scrolling. Brace confirms and explains how it breaks complex code into smaller methods, making it easier to manage. I’m struggling with the small keyboard, so I decide to switch to voice mode. Brace doesn’t miss a beat—pulls up special instructions for voice chat. Listening and speaking is way easier than dealing with the tiny screen and keyboard. Brace reads out the next code snippet, and I describe what I think is happening. It’s more conversational now, like I’m talking through the problem with a tutor. All I need to see on the screen are these crisp and clear block diagrams that Brace uses to illustrate the code structure. Move on to the next snippet—mention "Move Method" based on what I heard. Brace explains how moving a method to a more relevant class improves cohesion. The voice mode really helps me stay focused without getting bogged down by the interface. I miss a question on reading the code—just couldn’t make out the details on my screen. Brace moves on without fuss, focusing on the critical concepts instead. We hit on "Shotgun Surgery" next. Brace explains it, and then asks, "Which of these four classes is the only one that doesn’t need to be changed?" It’s tricky, but I give it my best shot, talking through my thought process. Finish up the assignment, reflect on what I’ve learned. Brace prompts me to submit—formats everything into a neat document. I submit and check Canvas for the summary. It notes that I skipped a code reading question but demonstrated the critical concepts later on. Overall, the summary highlights key points and insights, showing that I got the important parts down, even with the obstacles. Despite the challenges, the assignment turned into a solid learning experience. Now, I’m curious about how others handled it, especially those who didn’t have to rely on their phones. Each conversation must have been unique. Maybe I’ll run through it again when I have my laptop back, just to explore the other variations.
