Week 15 – The Reviews
This week was all about going through the results of our user testing and taking the first big steps toward applying fixes. With only five testers, you’d think the feedback would be light, but no, we got a ton of insight that really helped us see things differently. Now it’s about turning that feedback into working code while still pushing forward with the other parts of our project.
Feedback: We want to hear from you
The testers provided detailed notes that highlighted what was working, what wasn’t, and where things felt clunky. Some issues were small quality-of-life improvements, while others were bigger problems that made us stop and rethink the design. We took time this week to filter through all that feedback, categorize it into “quick fixes” versus “bigger changes,” and then prioritize what should be handled first.
One of the biggest takeaways? Even features we thought were solid could break once real users touched them. It was an eye-opener and really reinforced how important this testing phase is.
Fixes: Duct tape fixed everything
Once the feedback was sorted, we rolled up our sleeves and started implementing. Some examples of what got fixed this week include:
- Account & login flow: Tightening up logic that testers flagged as confusing or buggy.
- Bug squashing: Correcting a couple of crashes that happened when certain actions were repeated quickly.
- UI adjustments: Small tweaks to make navigation clearer.
It wasn’t just about patching holes; it was also about making sure those fixes didn’t create new problems. Every time we touched code, we tested again, double-checking the changes.
Algorithms: Still the bane of my existence
While the team was busy tackling fixes across the app, I spent most of my time working on algorithms. These are the backbone of how some of our feature’s process and display information. My goal this week was to refine them for speed and accuracy, making sure that data is handled efficiently.
It was definitely a challenge but rewarding too. Working on algorithms feels like building the engine of a car you may not always see it directly, but it powers everything else.
Team: Still Moving Forward
At the same time, the rest of the team kept progressing on their individual pieces of the project. Some were focused on polishing features, others on cleaning up code, and others still on making sure our dev branches stay synced. Even though we’re splitting tasks, it’s all moving toward the same finish line.
This teamwork makes it possible for me to dive deep into the algorithms while still knowing other parts of the app are moving forward.