03 / THE ENGINEERING PRACTICE

Architecture lab.

Complexity, made legible. Explore the boundaries that make a system work.

REFERENCE ARCHITECTURES

Conceptual models. These diagrams do not claim to represent a specific deployed project.

Product platform

A reference model for separating product interfaces, business logic and persistent data.

Client

The user-facing web or mobile interface.

05 / THE ENGINEERING PRACTICE

Beyond the application layer.

An interest in the complete machine. From the surface people touch to the systems underneath.

SOFTWARE ↔ SYSTEMS ↔ HARDWARE

Understand the layers.
Engineer the connections.

Product engineering reaches beyond an interface: APIs, persistent data, deployment and the environment where software runs.

Low-level topics are presented as research interests until project-specific work is documented.

C / Go / Assemblyx86_64 / ARM64 / RISC-VRTOS / OS bring-up
  1. 01User interface
  2. 02Application
  3. 03API
  4. 04Database
  5. 05Infrastructure
  6. 06Operating system
  7. 07Hardware

06 / THE ENGINEERING PRACTICE

Engineering in another dimension.

Spatial interfaces and real-time logic. An interactive laboratory, built into the portfolio.

LAB / 001 — SPATIAL INTERFACES

Software with physical presence.

This terrain is displaced in a GLSL vertex shader — the CPU never touches the mesh. The hero architecture, the technology constellation and the labs below are all live Three.js scenes rendered with React Three Fiber.

Three.jsReact Three FiberWebGL 2GLSLMediaPipe
Explore the live scene ↗

LAB / 002 — GAME ENGINEERING CONCEPTS

Rules. State. Emergence.

A seeded wave director spawns agents, drives them through spawn → advance → hold → retreat states around a player core, and escalates each wave. The simulation is plain TypeScript; the scene is one instanced mesh.

Game mechanicsProcedural systemsWave directorsPlayer stateMulti-tenant architectureReal-time logic

Demonstration built for this portfolio; shipped game titles are not yet published. Hand tracking and MediaPipe remain exploration topics.

Ten-sided column with four boolean-cut slots, hardened bevels, a champagne inlay ring and an emissive cap slit.

LAB / 003 — ASSET PIPELINE

From Blender to the browser.

Three assets authored in Blender from a reproducible bpy script — boolean cuts, hardened bevels, array modifiers, PBR and emissive materials — exported as glTF Binary and streamed into React Three Fiber with size normalisation, a turntable and contact shadows.

Blender 5 (bpy)glTF / GLBReact Three FiberPBR materialsEmissive accents

GPU-side work across the lab: GLSL vertex displacement, InstancedMesh crowds, physically based materials and soft contact shadows — all gated behind WebGL, viewport and motion preferences.

01 / THE ENGINEERING PRACTICE

How I work.

The whole system in view. Every technical decision connected to the product it serves.

01

Technology strategy

Define the product direction. Make technical decisions serve the business.

02

System architecture

Connect interfaces, services and data into a coherent system.

03

Product engineering

Carry a product from first interaction to working software.

04

Infrastructure

Treat deployment, reliability and maintainability as part of the product.

05

AI / automation

Apply intelligent tooling to useful, well-defined workflows.

06

Technical leadership

Bring clarity to decisions, implementation and delivery.

07 / ENGINEERING EVOLUTION

From the detail.
To the whole system.

My work has evolved from writing individual features to designing products, platforms and systems.

  1. 01Code
  2. 02Applications
  3. 03Products
  4. 04Platforms
  5. 05Systems
  6. 06Leadership