Another semester, another final reflection – TC3045 Reflection

Image from @ThePracticalDev under CC BY-NC

Is that time of the semester where I have to reflect on everything I know and everything I did. This course was interesting because I had the opportunity to dive deep into different topics and the opportunity to learn and even try different new tools.

From my own learning, I decided to do some of the mastery topics. In total, I did four of the six intended for the course. I chose the topics I liked the most, and the ones I thought I could not only look for information but have fun while writing about it, and even I could talk about my experience from it.

TC3045 is called Software Quality, and the first mastery topic was about learning about what software quality is. I wrote:

During the writing of this post, I defended my point of how Quality can be subjective, but at the same time, writing about this topic, I learned more in-depth about the ISO-2500, and even if I don’t really talk about other norms here, I started to look into them.

I didn’t talk about other rules, norms, or models to improve software quality because the second mastery topic was just about this stuff:

This post was the most difficult to write about. Even if it was interesting reading about it, summarize all information was complicated. It was really theoretical because doing something this practical would need a whole project and even a team to try to fix their workflows.

The next post I wrote about, I really loved to write about it. This was basically my whole experience during my last two FB internships when I need a review from someone, and everyone ignored me.

Compared with the other mastery topics, I just focused on having fun using a bunch of memes and talking about my experience in this one.

The last mastery topic I covered was about the tools that can be used to help on the quality during the development cycle:

Here, I focused on talking about tools I know, but I also had the opportunity to learn about new tools. The funny thing is that as time passes, all platforms implement new functions to cover even more parts of the software development cycle.

The last thing I wrote about in this blog about the course that wasn’t a reflection was doing a DevOps activity:

In the beginning, I was planning to skip this activity, but I have free time to do it, and actually, I have fun doing it. I have personal and work experience in this topic, but I got the opportunity to learn about the DigitalOcean platform and its tools.

On the other hand, we had several readings during the semester. In past reflections, I already talked about how I usually had general opinions rather than on specific points in the lecture, but the use of hypothes.is was really interesting and fun at some times. Using hypothes.is was a way to generate conversation, and even if it was an asynchronous one, it was interesting to have this social environment while learning. It was an opportunity to give our own perspective, discuss parts of the readings and even post some related memes.

A screenshot of a comment I did in one hypothes.is reading O RLY cover by @ThePracticalDev (Yeah, I love these images)

Speakers

The speakers were the most interesting part of the semester. Having the opportunity to learn from people’s experience in different branches of the CS fields was amazing. Some people weren’t that interesting to me, but I know other classmates really enjoyed those speakers, and the same the other way around. We had the opportunity not to just learn from things related to the course, but also the speakers touch different topics, sometimes completely unrelated to quality but related to CS fields, stuff we need to learn from life, and work experience.

Conclusion of the conclusion

This semester wasn’t the one I worked the most, but I have fun and have fun while learning, while doing my blog posts, while listening and asking stuff to speakers, and doing the reading. All things that may seem really boring in some other context, this semester was amazing, and I’m proud of what I did.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.