CST 340 - Week 7 Learning Journal
Part 1: Team Final Research Video Project Planning
Our team's planning process for the final research video project was a valuable learning experience in collaboration. We divided the responsibilities by giving each teammate a section of our presentation. We have collaborated through google videos. Communication was maintained primarily thought slack and weekly team meetings through zoom. The process was smooth in terms of idea sharing, but there were moments where coordinating schedules was difficult. I would suggest so every team member had the same timeline that we should have had regular check-ins. Overall, collaboration taught us the importance of balancing flexibility with structure. While creativity thrived in open discussions, timelines benefited from clear accountability.
Part 2: Reflections on Lectures and Activities
This week’s materials offered me a chance to connect technical knowledge with broader professional skills. The readings reminded me how important it is to combine careful planning, clear communication, and regular feedback in order to succeed in both academic projects and future career work. I saw the direct connection between these lessons and our team’s video project planning, where structure and accountability mattered just as much as creativity. Watching the TED talks also stood out to me because of the way speakers were able to turn technical concepts into powerful stories. It made me realize that being a software engineer is not just about solving problems but also about explaining ideas in ways that inspire and inform others.
The Harvard podcast on AI’s perils and promises pushed me to reflect more deeply on technology’s role in society. While AI can bring innovation and efficiency, it also raises questions about bias, transparency, and long-term consequences. As I prepare for a career in this field, I want to ensure that I contribute to AI systems that are ethical and fair. Finally, the presentation skills resources tied everything together by showing me that technical expertise is most impactful when it is communicated effectively. Confidence, clarity, and storytelling are essential, whether I am presenting a project to classmates or explaining software solutions to a future team.
Altogether, these activities reinforced the idea that engineering is not just technical work — it is also about responsibility, collaboration, and communication.
Comments
Post a Comment