CST 338 Learning Journey Summary

 During this class, I've learned a lot of valuable things. When I first started, I didn't think there would be much to gain since I've been working as a software developer for the past year and a half. I thought I had a solid grasp on using software design principles to write good code and develop large-scale systems. But as the course progressed, I realized how wrong I was. There were many areas where I could improve and many concepts I hadn't even considered before. For instance, teamwork is something I discovered I wasn't as good at as I thought. I found that I'm not always efficient or good at communicating when working with a team, and I'm still working on getting better at it, even though I initially believed I was pretty good in that area. 

This course has been a lot of fun and I found myself really getting into it during the second project, where we had to work with Android. Before this, I knew little about Android development, so diving into that environment was quite challenging. I love facing challenges, and this project was definitely one of those moments where I felt both excited and engaged. Another success I'm proud of is getting more comfortable with using Git. At my job, I've mostly used a proprietary software called EWM by IBM, so transitioning to Git and managing my projects with it was a significant achievement for me. It feels great to expand my skills and tools, especially with something as widely used in the industry as Git. Also I can say my teamwork skills improved a bit and I gained insights on how to work within a team on a fast paced development environment.  

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more