Skip to the content.

Trimester 2 Final

Tri 2 Final Blog


5 Key Contributions Over 12 Weeks

1. Dynamic Theme Management (CRUD Operations)

CRUD Implementation
I designed an interactive UI color-switching system to enhance user engagement. While default themes were available, I implemented a frontend color picker and a theme template, allowing each user to have a personalized theme. Users could update their themes seamlessly, and the frontend dynamically read and displayed these changes.

2. Deployment Administration

Deployment Blog
As the team’s Deployment Admin, I was responsible for successfully deploying our frontend. I first troubleshot and resolved local build issues that were preventing deployment. Once the build was stable, I used Cockpit to deploy the website efficiently, ensuring a smooth launch. To support my team, I created a detailed deployment blog documenting the challenges I encountered and their solutions. I also included issues faced by my teammates and provided clear instructions on updating backend code. This allowed the team to work independently without relying solely on me for future updates.

API Development

During the trimester, I developed my own API, a completely new experience for me. I structured it by adding files to the models and API folders, defining methods to interact with a custom database table I created. This API enabled seamless communication between the frontend and backend, allowing users to efficiently manage and update their theme settings.

4. Agile Methodology Implementation

User Story & Agile Planning
Kanban Board

At the start of the trimester, I developed a User Story to outline my feature goals and execution plan. I then maintained a burndown list and a Kanban board to systematically track progress, prioritize tasks, and stay organized throughout development.

5. Issue Tracking and Project Management

  • Burndown List
  • Feature CRUD Blog
  • Self-Assessment
    To stay accountable and structured, I created various GitHub Issues, including one for my User Story, issues for specific features, burndown lists, and even a self-assessment issue to reflect on my progress. This method helped streamline development and ensure no tasks were overlooked.

N@tM Feedback

One piece of feedback we received was from Yash Parikh:
Yash Parikh

Key Takeaway

“One thing you could work on could be making a style sheet that’s integrated with all of the pages.”

Next Steps for the Theme Feature

Currently, the theme system only updates the profile page, but it does not apply to other pages of the website. The next step in improving this feature is to create a global stylesheet that ensures the selected theme is applied consistently across the entire site.

Planned Improvements

  • Ensure the theme settings are fetched and applied on every page the user visits.
  • Implement a global theme system that affects all pages dynamically.

This improvement will enhance the user experience, making the theme system fully integrated and seamless across the application.


MCQ Review

Score Improvement

I scored 63/67, which is an improvement from my previous 55/66.
MCQ Score

Questions I Missed

I got the following questions wrong:

  • Question 11 (2.B) – Develop and Implement Algorithms
  • Question 21 (5.B) – Investigate Computing Innovations
  • Question 62 (2.B) – Develop and Implement Algorithms
  • Question 67 (4.C) – Evaluate and Test Algorithms and Programs

How I Improved

  • My overall score improved compared to my last attempt.
  • I dedicated around 2 hours to completing the MCQ section.

Areas for Improvement

  • Staying Focused – I need to focus more on the test and avoid letting my mind wander.
  • Reading Carefully – I zoned out on some questions and made careless mistakes.
  • Time Management – I should optimize my approach to avoid spending unnecessary time on certain questions.

ONWARD