Skip to main content

CST462S - From Learning to Impact: My Service Learning Journey

What went well during my service learning experience was my ability to contribute meaningfully to the ASCENDtials web team. I was able to complete several tasks such as updating website pages, working on LifterLMS courses, and improving user experience through better layouts and navigation. I also communicated effectively with my team, asked questions when needed, and stayed consistent with meeting deadlines. Over time, I became more confident using tools like WordPress, WPForms, and course-building platforms.

If I could improve something, it would be my time management and planning. There were moments when tasks felt overwhelming, especially when balancing schoolwork and service hours. I would also improve my confidence in decision-making, particularly when working independently on design or technical issues. Taking more initiative earlier and asking for feedback sooner would have made my work even stronger.

The most impactful part of this experience was seeing how my work directly contributed to a real organization. Knowing that the website updates and course improvements I worked on could help users and support ASCENDtials’ mission made the experience meaningful. It also helped me understand how technical skills like web development can be used in real-world situations beyond the classroom.

One of the main challenges I faced was that the tools, documents, and resources were not organized in one place. Everything felt scattered, and there was no clear guide or step-by-step process to follow. Because of this, I had to spend extra time figuring things out on my own by exploring the system, testing features, and learning through trial and error. While this helped me become more independent, it also made some tasks more time-consuming and confusing at the beginning.

My advice for future service learning students is to be prepared to figure things out on your own, especially if the tools and documents are not well organized. Don’t rely on having a clear guide—take initiative to explore the platform, test features, and learn through practice. At the same time, don’t hesitate to ask questions when you get stuck, as it can save you time. Staying organized on your end is very important, so keep track of links, notes, and instructions for yourself. Lastly, be patient and adaptable because real-world environments are not always structured, but that is also where the most learning happens.

Comments

Popular posts from this blog

CST438: Hands-On System Testing and Cloud Technologies

This week, I worked on both system testing and understanding cloud and distributed system concepts. One of the main things I learned was how to build Selenium system tests that simulate real user behavior. I created tests in which an instructor enters final grades and in which instructor-created assignments appear in a student’s view. While doing this, I learned how important it is to have all parts of the system running, including the frontend, backend, and external services like the gradebook. I also improved my debugging skills by fixing issues with Selenium, such as incorrect XPath selectors, missing UI elements, and unnecessary alert handling. I also learned how to properly manage my code using Git and GitHub. I created branches, committed my changes, pushed them to GitHub, and opened pull requests for review. This helped me understand a more realistic development workflow and how collaboration works in a team environment. In addition to coding, I reviewed several key concepts i...

WHERE I’m At: Midpoint Lessons in SQL and Beyond

 Halfway through this course, I can see how much I’ve learned and how it connects to both my past experiences and my future goals. One of the biggest takeaways has been understanding how SQL views work. I now know that a view is like a virtual table, useful for simplifying queries and presenting data, but usually read-only since it doesn’t store data itself. I’ve also learned the importance of normalization, which helps remove redundancy and ensures cleaner updates by splitting one large table into multiple related ones. Another valuable lesson has been comparing SQL with Java: SQL is declarative and focuses on the “what,” while Java is procedural and focuses on the “how.” This comparison helps me appreciate each language’s role in problem-solving. I’ve also seen firsthand how powerful SQL can be in real workflows compared to spreadsheets, such as enforcing business rules like course eligibility in a single query. Beyond SQL, I’ve grown as a programmer in general—planning better, w...