HTML
Structure & accessibility
I focus on semantic markup, meaningful headings, and screen-reader friendly layouts. Most of my projects start with clean HTML before any styling or JavaScript is added.
Good projects are more than code snippets. They come from choosing the right tools, understanding how they fit together, and using them in a way that stays readable when someone opens the repo a year later.
This page gives a high-level view of the languages, tools, and platforms I use most often. It is not meant to be a buzzword dump. These are the technologies that actually show up in my projects and classwork, from basic HTML layouts to full-stack apps deployed to the cloud.
The foundations I reach for when building the front end of a site, experimenting with logic, or automating small tasks.
Structure & accessibility
I focus on semantic markup, meaningful headings, and screen-reader friendly layouts. Most of my projects start with clean HTML before any styling or JavaScript is added.
Layout & design systems
I rely on Flexbox and Grid for layout, keep colors and spacing in CSS variables, and aim for responsive designs that behave well from mobile through desktop.
Interactivity & logic
From DOM manipulation to API calls and simple game loops, JavaScript is where most of the interactivity in my projects lives. I prefer small, focused modules over giant files.
Scripting & backend practice
I use Python for scripting, data-heavy exercises, and backend prototypes. It shows up in projects like my Sudoku game and lab tooling for pipette calibration.
Tools that help me move faster while staying in control of what the code is actually doing.
Component-based interfaces
I use React with Vite when I need stateful interfaces, such as the Visual Daily Scheduler concept. I aim for clear component boundaries and predictable data flow.
Fast dev tooling
Vite gives me quick builds and a smooth dev experience when working with modern JavaScript or React projects, especially those I plan to grow over time.
APIs & tooling
I use Node.js for small backend services, build scripts, and working with APIs like OpenWeather, TMDB, NASA, and OpenAI.
Where my projects live and how I keep API keys and deployments under control.
Version control
I use Git for branching, commits, and pull requests, with GitHub as my primary place for collaboration, issues, and project documentation.
Secure API proxies
I proxy external APIs (NASA, OpenWeather, OpenAI, TMDB) through Workers so keys stay server-side and the browser never sees sensitive credentials.
Full-stack deployment
Render hosts my full-stack projects, including Node/Express backends and Vite-built frontends, keeping everything in one place with simple deploys.
The tools that make it realistic to balance school, projects, and experiments without losing track of what I am doing.
Primary editor
VS Code is where I spend most of my time: linting, formatters, Git integration, and extensions tuned for web development and Python work.
Debugging & performance
I use DevTools for layout inspection, network requests, performance checks, and testing how interfaces respond at different screen sizes.
Task tracking
Simple task lists and project notes help me keep school assignments, portfolio ideas, and long-term experiments moving in the right direction.