CST 462 - FINAL WEEK

 Hey everyone!

What went well?
One of the most positive aspects of my Service Learning experience was the opportunity to contribute meaningfully to a real-world open-source project—LibreOffice. I gained hands-on experience with bug testing and bibisecting, and felt a strong sense of accomplishment when I successfully identified the root of a table formatting bug. Collaborating with an active community and receiving feedback on my contributions was both encouraging and motivating.

What would you improve?
If I were to do this again, I would spend more time early on familiarizing myself with the project’s communication channels and workflow. It took a while to fully understand the bug tracking system, how to navigate the codebase, and the expectations for filing reports. A more structured onboarding guide or peer mentor would have helped speed up the process.

What was the most impactful part?
The most impactful part of the experience was realizing how open-source work supports users around the world. Every bug report, every fix, every test contributes to software that empowers people—especially in communities that rely on free and open tools. Being part of that global ecosystem, even in a small way, was eye-opening and inspiring.

What challenges did you face?
One major challenge was the technical learning curve. LibreOffice is a large and complex codebase, and understanding how to use debugging tools and the bibisect repositories was initially overwhelming. Additionally, working independently required a lot of self-motivation and time management to stay on track.

What advice do you have for future SL students?
Start early and don’t be afraid to ask questions. The open-source community is welcoming, but it’s up to you to reach out, stay engaged, and communicate your progress. Also, keep a record of what you’re doing each week—it helps when writing your reflections and shows how much you’ve learned. Most importantly, be open to learning through trial and error. Every small task you complete builds confidence and skills.

See you next time!

Comments

Post a Comment

Popular posts from this blog

CST 334 - Week 6

 Hey everyone!      This week we submitted our research collab project. It was quite interesting and fun. I learned a lot and our team bonded more as well. We also learned many new things through our lectures and labs.       Concurrency is a critical concept in computer systems, enabling multiple processes to execute simultaneously. However, with great power comes great complexity.       A semaphore is a synchronization primitive that helps manage access to shared resources in a concurrent environment. Semaphores can be thought of as counters that control the number of processes allowed to access a resource. They come in two main types :             - Counting Semaphores : These can have values greater than one and are often used to manage a   pool of resources, such as threads or connections.           - Binary Semaphores : These function like locks and c...
Read more

CST 334 - Week 4

Hey everyone!       This week, I learned about how operating systems manage memory, which is one of their most important jobs. One topic was free space management , where the system keeps track of memory or storage that isn’t being used. Two common methods are bitmaps (using bits to mark if memory is free or taken) and linked lists (connecting free memory blocks together). Each method has its pros and cons, like how much space they use or how fast they work.      I also studied paging , which splits memory into small chunks called pages. These pages are mapped to physical memory, keeping processes separate and organized. However, this mapping can slow things down because the computer has to translate addresses often. To make it faster, Translation Lookaside Buffers (TLBs) store recent translations in a small, quick cache. I also learned about advanced page tables , which are smarter ways of organizing these mappings to save memory.    ...
Read more

CST 370 - Week 1

 Hey everyone, This week, we learned several important topics that form the foundation of computer science and programming. We started with GitHub and practiced using manual commands like git init, git add, git commit, and git push to manage our code. This helped us understand version control and how to keep track of changes when working on projects, especially when collaborating with others. We were also introduced to algorithms and learned what they are—step-by-step methods for solving problems. One example we focused on was Euclid’s Algorithm for finding the greatest common divisor (GCD) of two numbers. It uses a simple but powerful idea: repeatedly replace the numbers with GCD(b, a % b) until the second number becomes zero. We also practiced writing pseudocode, which helped us plan out algorithms in plain language before coding. We also had a homework assignment to help us further understand GitHub commands. Later in the week, we learned about graphs, both weighted and unweight...
Read more