ENGINEERING / HOW I THINK

Make the complexity
earn its place.

Systems should be understandable, failures should be recoverable, and tools should help people do their best work.

Good engineering
is invisible.
Until it matters.

I care about what happens after the first impression. How a system grows. How a team works in it. How it behaves when things go wrong.

01 /

Architecture with intent.

Boundaries that earn their place. Components that compose. State that lives where it belongs.

02 /

Fast is a feature.

Measure the actual bottleneck, ship less JavaScript, and keep the critical path short.

03 /

Built for the next engineer.

Clear contracts, useful documentation, and a local setup that gets out of the way.

04 /

Reliable by design.

Make failures visible. Validate at the boundary. Give people a clear way to recover.

05 /

Product before abstraction.

Understand the workflow first. Make the useful thing feel obvious. Let real needs shape the system.

06 /

AI with accountability.

Use AI to explore, draft, and accelerate. Verify behavior, protect context, and own every decision.

The tools change.
The thinking stays.

A foundation in frontend systems, extended through hands-on product building.

01

Architectural & Concepts

Micro-Frontends (MFEs) / Enterprise UI Design Systems / Performance Optimization / Server-Driven UI / System Design / Scalable Component Architecture / Workflow Management System / Configurable UI

02

Front-End Frameworks

Angular / React / Redux

03

Languages

JavaScript (ES6+) / TypeScript / HTML5/CSS3

04

Backend & infrastructure

Node.js / SQLite / Electron / Docker
Applied across the product ecosystem

05

AI & engineering practice

AI-assisted tooling / Boundary validation / Accessible interfaces
Product evidence in Atlas, Prism and Envision

Decisions in practice.