Gerek's ByteTrail Oydssey

Time really does fly. This will be my final journal entry, and it marks the end of Gerek’s “byte trail” and undergraduate journey in Computer Science at CSUMB. Looking back, I can see how much I’ve grown both technically and professionally. I’m glad I was encouraged to keep a journal because now I’m able to look back on my past entries to reflect on my growth. Throughout the program, I’ve developed a strong foundation in core computer science concepts like algorithms, data structures, databases, operating systems, networking, and software engineering. I learned important concepts for being a competent software engineer like documentation, testing, and clean code habits. I plan to carry these forward into my career. As I close out my chapter at Cal State Monterey Bay, I’m excited about the opportunity to step into the tech workforce. It seems learning in this field never truly stops, and I expect my education to continue evolving throughout my career as technology advances. I’m partic...

My Service Learning experience was quite rewarding. Through the Document Foundation I was able to learn how real-world software projects operate from the scope of a tester. By contributing to LibreOffice QA, I gained hands-on experience with bug triaging and reproducing issues across different operating systems. This helped me better understand the workflow on collaborative software projects. I think the most impactful part of this experience was realizing that meaningful contributions do not always require intensive engineering.  I was still able to support developers and improve the software quality by testing, reproducing bugs, and leaving detailed comments in Bugzilla,. This reinforced the idea that quality assurance, testing, and documentation are just as critical as development itself. One of the main challenges I faced was the learning curve associated with tools like bibisect repositories and setting up consistent testing environments across Windows and Linux. At times, tro...

This week, our team finalized the core deliverables for the Capstone project. We completed and submitted the testing report, incorporating client-based testing feedback, deployment validation, and individual contribution sections aligned with the rubric. We also adjusted our Capstone Festival presentation slides and recorded a polished final presentation video. I  quickly resolved some audio issues and ensured the video was accessible. The project is in a presentation-ready state and it seems major requirements are satisfied.

This week, our team met with our clients Tian & Shuhe to go over the remaining parts of the project as we move toward final submission. During the meeting, we discussed the two different types of tests that will be conducted: a user test performed by Shuhe and a deployment test conducted by Tian himself. This meeting helped us understand what each evaluation will focus on and what we need to prepare for. Tian also requested that we create documentation for the project, specifically a README with a developer-oriented quickstart guide. I contributed to planning the structure and content of that documentation and began outlining what developers will need to quickly understand and run our system. Next week, our main focus will be making the README file, including setting up clear quickstart instructions. I will help consolidate our existing notes, scripts, and architecture explanations into a clean and easy-to-follow document. At the same time, we will begin preparing material for the ...

This week, I focused heavily on the automation and testing side of our Capstone project. I finalized the automated bi-monthly deployment pipeline by debugging environment inconsistencies but I ultimately getting the entire scheduler running successfully on Linux. I added header comments to the automation scripts that will need to be run on the host server.  I also contributed unit tests with pytest. Each team member took up the task of creating unit tests for each of our 4 core services. I worked on unit tests for the summarizer. This included tests for sentence cleanup, stripping Chinese notes, markup removal, and edge-case handling with short or markup-heavy inputs. Next week, my plan is to assist with any last-minute fixes needed for incremental updates or environment setup, and help polish our final presentation. I will be completing the Conclusion & Closing section of the project. We may potentially use Playwright for end-to-end test coverage, but we still need to talk abo...