Julien Massaux – Culmination Final Thoughts

After completing all of the work this semester, I’ve come away with several lessons—some expected, many not. One thing I’ve discovered is that app development may not be the path I want to pursue long-term. However, what I’ve gained from this experience is far more valuable than just technical know-how.
Working closely with my project partner taught me a great deal about collaboration, accountability, and adapting under pressure. We both made sacrifices throughout the semester to ensure progress was made. Admittedly, there were moments when we lost track of time, misjudged deadlines, or let our productivity slip. Some parts of the project were far more difficult than anticipated, and the time we thought we had in abundance early on disappeared quickly. In the beginning, we made rapid progress, finishing large sections with polish and enthusiasm. For a time, it felt as if we could complete the entire thing ahead of schedule. But as things often go, overconfidence gives way to unforeseen challenges.
We made promises to ourselves and to each other that proved harder to fulfill than expected. I had high hopes for what our app could become—something elegant, complete, and while I’m still content with what we accomplished, it’s fair to say it didn’t quite reach the ideal vision we once imagined. That’s often the nature of creative or technical work: the final product rarely aligns perfectly with the dream you start out chasing.
The one-on-one sessions with professors were an especially valuable part of the development process. Their specialized knowledge—whether in music, Unity, or general programming—provided focused guidance that the broader project panel couldn’t always offer. These meetings helped us establish a clear direction for our work, especially when we felt uncertain or overwhelmed by the project’s scope.
While the panel played an important role in offering external perspectives—helping us see how a first-time user or outsider might interpret the project—the feedback from professors was more nuanced and directly applicable to our technical and creative challenges. They were able to dive into the specifics of our implementation, point out potential pitfalls, and offer suggestions that came from real expertise in relevant domains.
These conversations not only clarified difficult concepts but also helped reignite motivation at times when the project felt stalled. It was through this kind of direct engagement that we were able to refine our ideas and move forward with greater confidence. The combination of general audience feedback from the panel and expert insight from our professors created a balanced support system throughout the development journey.
I’ve also gained a better understanding of my own work habits. I realized how much I rely on external motivation, and how difficult it can be to push through tasks that don’t personally inspire me. This project highlighted areas where I need to grow, especially when it comes to staying consistent and driven regardless of how I feel about the subject matter. My partner and I depended on each other, and there were times when I knew I didn’t contribute as fully as I could have. Still, we got it done, piece by piece. I handled tasks like implementing leaf animations, designing color transitions, and bending branches—features I genuinely enjoyed working on. They gave me a creative outlet in a project that otherwise felt routine at times.
Ultimately, I’m glad to close the chapter on this particular app. It was a stepping stone, and I know that future projects will be even more complex and demanding. One of the key lessons I’ll carry forward is that waiting for inspiration isn’t always realistic—especially when working under deadlines. If the work isn’t exciting, that doesn’t mean it isn’t important. Sometimes the difference between stability and struggle lies in doing what needs to be done, regardless of how compelling it feels in the moment.
If I could go back, I might choose a project more aligned with my own interests. The concept was interesting—meditation and nature-based interaction—but it wasn’t something I personally connected with. That lack of connection made the work feel less engaging at times. Still, I’m proud of what we delivered. I didn’t mind the slower weeks, nor did I mind presenting to the review panel. I’ve always been good with people and communication, and I leaned into that strength during our presentations.
This project didn’t just teach me about code or app design—it gave me insight into who I am as a teammate and contributor. It exposed areas for growth, but also highlighted what I’m capable of when I push through. I may not have excelled in every way, but I came away with lessons I know will serve me well going forward.