My Projects
This page highlights project stories, decisions, and growth. For full technical bullet details and complete chronology, please view my resume.
In Progress: Sophisticated Portfolio
Story: I am actively designing my new portfolio as a more immersive and expressive experience inspired by the interface language of DOTA 2. The goal is to push my front-end and interaction design skills beyond a standard personal site and turn the portfolio itself into a product.
Current focus: I am currently prototyping page layouts, interaction patterns, and content hierarchy to make sure the visual style stays bold while the site remains easy to navigate.
Next milestones: Integrate playable project embeds, polish key interactions across desktop and mobile, and run a focused usability pass on navigation clarity.
What I'm exploring now: How to balance expressive visual direction with readability, storytelling flow, and intuitive interaction decisions.
Static Site Generator
Story: I built this static site generator to make my portfolio easier to maintain through writing instead of manual page edits. It parses markdown content and turns it into a consistent static site so updates can happen quickly.
Impact: This workflow lowered friction for publishing and iterating on content, especially for pages like now, where regular updates should feel lightweight and sustainable.
What I learned: Developer experience matters even in personal tooling, and a simple content pipeline can make long-term maintenance much more realistic.
Othello Game
Story: Othello began as an AI class project with terminal-based interaction, then evolved into a web application so the game experience matched the quality of the underlying logic. I transitioned it from a script-style demo into something users could play visually and intuitively.
Impact: Moving from terminal input to a browser interface made the project more accessible and more representative of production-minded product work, not just algorithm implementation.
What I learned: Productizing technical work often means rethinking interface and interaction, not only improving the core logic.
VisQuiz
Story: VisQuiz was my major qualifying project and a core experience in connecting full-stack implementation with research goals. I helped build the quiz platform, capture participant interaction data, and support the analysis workflow behind the study.
Impact: The project produced both a working research tool and publishable findings on graphical interpretation development, bridging software delivery with academic output.
What I learned: Building for research requires balancing engineering quality with experimental rigor so the final insights are both reliable and actionable.
Choice Decider
Story: Choice Decider was my first end-to-end full-stack team project, where I worked with three teammates to build a complete web application with backend logic, APIs, persistence, and front-end interaction.
Impact: The project became a milestone for ownership growth because we had to divide responsibilities intentionally, coordinate dependencies, and still ship a coherent product together.
What I learned: Leadership starts early in project work through clear delegation, communication, and keeping both delivery and team learning outcomes in view.
More about me
Home | Now | Experience | Resume