Hi, I'm .
I build |

01 — About

02 — Selected work

AI, cloud & financial modeling

Click any card for details. Filter by discipline.

03 — Model lab

Valuation models

Two full equity-research models you can download and audit, plus a live DCF sandbox to play with.

Interactive DCF sandbox

A live five-year discounted-cash-flow model. Move the sliders and the enterprise value, cash-flow chart and sensitivity grid update instantly.

Projected free cash flow

FCF PV of FCF

Sensitivity: enterprise value

WACC ↓ × terminal growth →

04 — Cloud & DevOps

What I've deployed, and how

For hiring managers and clients: live deployments, the architecture behind this site, my bootcamp capstone, and where each cloud skill is demonstrated.

Architecture of this website

A static front end with a serverless back end on two clouds.

Swipe sideways to see the full diagram →

Request flow: GitHub Pages serves the site; the contact form posts to Azure Functions first, fails over to AWS Lambda, then to the visitor's email app. GitHub Pages Static HTML · CSS · JS HTTPS · global CDN Visitor's browser Validates the form Tries each API in order 10 s timeout per cloud Email-app fallback mailto: with message filled in so no enquiry is lost MICROSOFT AZURE · PRIMARY South Africa North Azure Functions Flex Consumption (serverless) .NET 10 isolated worker CORS: this site only Rate limit · spam honeypot Table Storage · stores every message Communication Services · email Application Insights · telemetry AMAZON WEB SERVICES · FAILOVER eu-west-1 · Ireland AWS Lambda Function URL (HTTPS) .NET 10 · arm64 Same shared core library Built with SAM / CloudFormation DynamoDB · stores every message Amazon SES · email CloudWatch Logs · 30-day retention 1 2 3 4
  1. Load: GitHub Pages serves the site as static files: nothing to patch, HTTPS by default.
  2. Send: the contact form posts to Azure Functions, which stores the message, then emails it.
  3. Failover: if Azure times out or returns a server error, the same request goes to AWS Lambda.
  4. Last resort: if both clouds are down, the visitor's email app opens with the message filled in.

Application architecture

Swipe sideways to see the full diagram →

Ballot architecture: the browser reaches an Nginx + React frontend on EC2, which proxies to a Flask API backed by PostgreSQL and Redis; a Node.js worker consumes queued votes from Redis and writes them to PostgreSQL. Voter / admin browser AWS EC2 · DOCKER COMPOSE · 5 HEALTH-CHECKED SERVICES CloudWatch logs & alarms Frontend React + Nginx · port 80 Flask API JWT · admin roles PostgreSQL users · elections · votes Redis reservations · queue · cache Node.js worker writes votes in a txn /api queue vote job commit

CI/CD pipeline (GitHub Actions → AWS)

    Engineering highlights

    What we'd build next

      Cloud skills, and where to see them

      05 — Experience

      Where I've delivered

        06 — Skills

        Toolkit

        07 — Education & credentials

        Foundations

        08 — Contact