Backend-leaning software engineer who likes building things from the database layer up to the user-facing workflow, with a strong side of C/C++, Qt, systems debugging, and automation.
I started backend work with Infinite Vocabulary, then kept pushing into fuller systems: layered Flask APIs, Spring Boot services, Dockerized full-stack apps, Qt desktop tools, telemetry dashboards, and low-level experiments where the debugger matters as much as the code.
- Backend APIs with clear layers, validation, authentication, and real data models.
- Full-stack systems that connect product workflows to databases, storage, and deployment.
- Qt/C++ desktop apps for telemetry, media, networking, file I/O, databases, and model/view UI.
- Automation tools for developer workflows, builds, scraping, and local system setup.
- Low-level C/C++ projects: compilers, algorithms, systems debugging, and ALX C fundamentals.
| Project | What it does | Stack |
|---|---|---|
| Infinite Vocabulary | My first backend API: vocabulary, categories, scoring, leaderboard, search, Firebase auth, and admin/student management. | Flask, Pydantic, Firebase Auth, Firestore, Google Cloud |
| CPMSS | Full-stack compound management system with backend workflows, object storage, migrations, docs, and local stack automation. | Java 21, Spring Boot, PostgreSQL, Flyway, SeaweedFS, Next.js, TypeScript, Docker |
| Qt6 Projects | Project-based Qt6 curriculum covering core Qt, widgets, QML, model/view, SQL, threading, networking, multimedia, and capstones. | C++, Qt6, QML, CMake, QTest |
- Image Processing Toolbox: C++17 desktop app for live image filters using OpenCV, SDL2, and custom UI.
- S-VCS: local version-control simulator with diff storage, backup sync, restore, and conflict handling.
I am sharpening the overlap between backend engineering and systems work: APIs with real data contracts, desktop tooling that talks to hardware or the OS, and automation that makes development less repetitive.