Education

UBC — BA in Computer Science

Bachelor of Arts in Computer Science at The University of British Columbia (Sep 2023 – Apr 2028). Broad CS foundation across networking, algorithms, databases, operating systems, software engineering, and computer graphics, paired with frequent project-manager roles in team coursework — splitting tasks fairly, assigning them clearly, and keeping deadlines on track.

  • Networking
  • Algorithms
  • Databases
  • Operating Systems
  • Software Engineering
  • Computer Graphics
  • Project Coordination
  • Deadline Management
  • Cross-Domain CS
Live Demo TODOGitHub TODO
Visual Placeholder

Education

Overview

Project Context

A recruiter-friendly breakdown of the product goal, audience, and engineering direction.

Overview

What it is

Bachelor of Arts in Computer Science at The University of British Columbia (September 2023 – April 2028, CS major).

Who it is for

Built for someone who wants broad CS depth first, then applies it across industries and project types — including the Naxa internship and personal full-stack projects (TokyoQuest, HHU).

Why it matters

Specializing too early narrows the problems an engineer can credibly take on. A wide CS base makes it easier to combine ideas across systems, algorithms, databases, and product constraints.

Problem

What needed to be solved

It's common to specialize early and become strong in one stack, but weaker at connecting systems, algorithms, databases, team workflows, and product constraints when a real project demands all of them at once.

  • Narrow specialization early can limit which problems an engineer can credibly take on.
  • Theory-only learning rarely transfers cleanly to messy team and infrastructure realities.
  • Implementation-only focus leaves planning, sequencing, and deadlines as someone else's problem.

Solution

Product Approach

Use the UBC CS curriculum to build broad, named foundations across networking, algorithms, databases, operating systems, software engineering, and graphics — then translate each course into a habit that shows up in real engineering and team work.

Main User Flow

  1. 01Take a deliberately broad set of CPSC courses instead of niching down early.
  2. 02Translate each course into a concrete engineering or team habit.
  3. 03Carry those habits into team coursework and into the Naxa internship + personal projects.
  4. 04Hold specialization (e.g. AR, blockchain) for later, after the breadth foundation is in place.

Key Decisions

  • Pick CS breadth (networking + algorithms + databases + operating systems + software engineering + graphics) over early specialization.
  • Treat team coursework as practice for project management — fair task splitting, clear assignment, and deadline tracking.
  • Use CPSC 317 (Networking) and CPSC 313 (Computer Hardware and OS) as the bridge between coursework and infrastructure / cloud work in industry.
  • Keep AR and blockchain on the future-deepening list, not the current main track.

Features

Key Product Capabilities

↗

CPSC 317 — Networking

Deepened networking fundamentals and infrastructure understanding. Carries over directly into cloud work (e.g. AWS) on real projects like the Naxa internship.

↗

CPSC 313 — Computer Hardware and Operating Systems

Built a lower-level mental model of how programs actually run — memory, processes, and OS-level behavior — which makes infrastructure and performance reasoning more concrete.

↗

CPSC 320 — Algorithms

Built stronger problem decomposition and performance-aware decision making for everyday implementation choices.

↗

CPSC 304 — Database Architecture

Studied database design and querying so data modeling decisions in real projects are grounded in fundamentals, not just ORM defaults.

↗

CPSC 310 — Introduction to Software Engineering

Studied technical debt and team development practices — habits for keeping codebases maintainable and collaboration smooth.

↗

CPSC 314 — Computer Graphics

Expanded perspective beyond standard web/backend tracks into visual and interactive computing.

↗

Project-Manager Role In Team Coursework

Frequently took the implicit PM role — splitting tasks evenly, assigning them clearly to teammates, and managing per-task deadlines so the group hit the overall deadline.

Key features

Impact / Results

  • Built a broad CS foundation across networking, algorithms, databases, operating systems, software engineering, and graphics rather than over-specializing early.
  • Connected CPSC 317 (Networking) and CPSC 313 (Computer Hardware and OS) to real cloud infrastructure understanding used in the Naxa internship's AWS + Terragrunt work.
  • Connected CPSC 304 (Database Architecture) to data modeling decisions in personal full-stack projects (TokyoQuest, HHU).
  • Practiced task splitting, assignment, and deadline management in team coursework — habits that translate directly into shipping real product work.

What I Would Improve

  • Keep deepening breadth across CPSC tracks before locking into a single specialization.
  • Later, deepen Augmented Reality and blockchain in particular while keeping a cross-domain CS perspective.
  • Capture course projects more carefully (links, reports, demos) so the academic work is verifiable from the portfolio.

Impact and future improvements