The Short Version
I am an AI-focused builder creating a portfolio that turns training, capstones, and project work into something more reviewable and more useful than static notebook submissions. I care about the build itself, but I also care about how the work is explained, staged, and presented so another person can actually understand what I did.
I work across applied data science, machine learning, deep learning, browser-based demos, and the portfolio layer that connects everything together. That means I am not only training models. I am also shaping the architecture, artifacts, documentation, and delivery experience around them.
What I Focus On
Applied model work
I build around classification, computer vision, deep learning workflows, and staged experimentation that can be shown clearly.
Presentation and delivery
I turn project outputs into structured pages, reviewable artifacts, and live demos so the work can stand on its own.
Architecture and persistence
I care about permanence, reproducibility, and keeping the source of truth inside the project instead of relying on one-off fixes.
Clarity for reviewers
I focus on making technical work easier to follow, especially when there are multiple models, tradeoffs, or project lanes involved.
Resume Snapshot
AI Engineering Portfolio Builder
Current focus
I am building an end-to-end portfolio that combines AI project execution with strong web presentation, artifact handling, deployment discipline, and live browser demos.
Microsoft AI Learning Path
Training foundation
My recent work is anchored in Microsoft certifications, applied AI coursework, and capstone-driven implementation across data science, machine learning, and deep learning.
Portfolio-Ready Project Work
Representative examples
Published examples include autonomous driving object detection, vessel classification for port operations, and a 3-class face mask detector with browser-based demo support.
Technical Strengths
Tools and delivery
I work with Python, TensorFlow, Keras, PHP, Bootstrap, GitHub, Colab, and browser-side inference patterns, with a strong emphasis on structuring work so it is easier to review and maintain.
How I Want The Work To Feel
Honest
I prefer showing the real trial-and-error path, including weaker attempts and model comparisons, instead of pretending the first result was perfect.
Understandable
I want someone reviewing the site to understand the objective, the method, the result, and the reason behind the final choice without digging through raw notebooks alone.
Permanent
I value work that survives refreshes, redeploys, and future edits. That is why I spend time on structure, repeatability, and source-controlled delivery.
Where To Go Next
If I want to show the strongest proof of work first, the best next stops are the published projects, the live demos, and the featured certificates page. Those three areas do the best job of showing both technical execution and presentation quality.