Build Log

Before I go deep on each piece, here's the recap. My portfolio isn't just a page. I built it like a product.

What that means:

• → My own domain, configured by me (DNS, SSL, all of it)
• → Self-run hosting, not someone else's platform
• → My own first-party analytics, not a borrowed tracker
• → A private live dashboard that only I can see

The catch: none of these are "set and forget." Each one is a system I own and have to maintain myself.

What I learned: owning the infrastructure is more work than using a template, but it means I control exactly what gets tracked and how the site behaves. No black box.

I attached a poll asking which deep dive to write first. The vote picked hosting and analytics, so that's the order the next parts follow.

My work was spread across GitHub, OneDrive, iCloud, old coursework folders and client files. More than a dozen projects: SQL, Python, Power BI, Tableau, Grafana, Excel, AWS.

The hard part was deciding what stays and what goes.

My rules:

• ✅ Keep it if it solves a real problem
• ✅ Keep it if I can explain every step
• ❌ Cut anything that needs a paragraph of excuses

What I learned: it turned out to be an analytics task too. Messy inputs, clear criteria, a smaller and better output.

Recruiters spend seconds on a resume. "Built executive dashboards" and "ran a Six Sigma analysis" read the same on every page. The thinking behind them doesn't come through.

So I gave myself a sprint: turn years of scattered projects into one portfolio where you can open the work and watch it run.

That's this site: fourteen live demos, every figure recomputed in your browser from the raw data, and a resume you can query in SQL.