CST462 Service Project Reflections

    One thing that went well during our service-learning project was our ability to build meaningful full-stack functionality that contributed to a real application rather than just completing isolated assignments. As a team, we developed useful features such as availability scheduling, time entry reporting, and backend APIs to support booking functionality. Collaboration improved over time as we became more comfortable using Git, resolving merge conflicts, and coordinating contributions through pull requests. A major success was moving portions of the project away from hardcoded or mock data toward real frontend-backend integration. We also made significant progress through debugging, identifying issues involving authentication, CORS, and data persistence that led to real improvements in the application.


    One area I would improve is communication and coordination earlier in the development process. There were times when better communication about branches, feature ownership, and merging strategies could have reduced confusion and prevented integration issues. I also learned the importance of syncing with the main branch frequently and testing integration points earlier, rather than waiting until multiple features are developed in parallel. Personally, I would like to continue improving my Git workflow, debugging strategies, and API design skills. Better documentation throughout development would also have made collaboration and handoffs smoother.


    The most impactful part of the project for me was seeing how backend work could directly support other parts of the system and other teammates. Building features like the availability slots API and weekly reporting endpoint showed how backend development could power frontend functionality and improve the overall product. Debugging and resolving the issue where frontend availability changes were not persisting to the backend was especially impactful because it addressed a real system-level problem and helped move the project closer to functioning as intended. It was rewarding to contribute work that had visible effects beyond just my portion of the codebase.


    One of the biggest challenges we faced was coordinating work across multiple contributors while the codebase was evolving. Merge conflicts, branch synchronization, and overlapping changes created difficulties at times. We also faced technical challenges involving frontend-backend integration, authentication, and debugging situations where the user interface appeared correct even when the backend data was not. A major lesson from these challenges was that many software problems are not purely coding problems, but integration and communication problems that require collaboration and careful troubleshooting.


    My advice for future service-learning students is to communicate often, sync with the main branch regularly, and test integrations early. It is easy to assume different parts of a system are working together when they are not, so validating end-to-end behavior is important. I would also recommend using Git branches and pull requests consistently and keeping feature branches small to reduce conflicts. Another lesson is not to underestimate debugging work—finding and fixing hidden issues can be just as valuable as building new features. Finally, focus on contributions that support the team and the project as a whole, because some of the most rewarding work comes from solving problems that help everyone move forward.

Comments

Post a Comment

Popular posts from this blog

Computer Science BS Journal (CST334) : Week 3

  This week in CST334 our lectures covered: Address Spaces, C Memory API, Address Translation & Base-and-bounds, Segmentation, Free Space Management. We also started working on our first group project this week. In this learning journal I'll write and explanation/what I think to be the most important bits of each subject. 1. Address Spaces An address space is the range of memory addresses that a process can use. Each process has its own virtual address space, isolated from others, managed by the operating system. Key Takeaways: Provides process isolation . Helps with security and stability . Enables virtual memory and memory protection. 2. C Memory API The C memory API includes functions for dynamic memory allocation and deallocation: malloc() , calloc() , realloc() , and free() . Key Takeaways: malloc(size) allocates a block of memory. calloc(n, size) allocates and zero-initializes memory. realloc(ptr, new_size) resizes previously allocated memory. ...
Read more

Computer Science BS Journal (CST334) : Week 5

    This week in CST334 our lectures covered: Concurrency and Threads, Threads API, Locks, and Lock-based data structure. In this learning journal I'll write and explanation/what I think to be the most important bits of each subject. We also had our midterm this week and I didn't do as good as I wanted to, I definitely need to focus some more on my studies. Concurrency and Threads Concurrency is the ability of a system to handle multiple tasks at the same time. Threads are the smallest units of execution within a process. Concurrency allows threads to run independently, improving efficiency, especially on multi-core processors. Key Takeaways: Concurrency enables better CPU utilization. Threads share the same memory space within a process. Context switching allows threads to appear to run in parallel. Can lead to race conditions if not properly synchronized. Threads API Threads APIs provide the functions and mechanisms to create, manage, and synchronize threads....
Read more

Computer Science BS Journal (CST363) : Week 2

 Class: CST363-30_2253 ( Intro to Database Systems) SQL has the flexibility to join tables on any column(s) using any predicate (=, >, < ).    Most of the time the join will use equality between a primary and foreign key.   Think of example where joining on something other than keys would be needed.  Write the query both as an English sentence and in SQL.  If you can't think of your own example, search the textbook or internet for an example. English Sentence: Imagine you are working with a database that stores information about employees and their salary performance. You may want to find the employees who are earning more than the average salary in their department. In this case, you would join the employee table with the salary data table using the salary amount, not the keys, in order to compare each employee's salary with the department's average. Query:   SELECT e.employee_name, e.department_id, s.salary FROM employees e JOIN salaries ...
Read more