Kuala Lumpur, Malaysia--:--:-- UTC+8

ENGINEERING SYSTEMS, SHIP BY SHIP.

HOVER & DRAG TO INTERACT

LUCASDENGYI JIN

Precision structure, bold execution. Full-stack systems with race-pace delivery.

About

Engineered narrative, product instinct.

Systems bridge

Hero motion → capability grid. Same discipline: telemetry-first surfaces, readable under load.

I build full-stack platforms where telemetry, contracts, and craft come together. Those systems stay legible at race pace and calm when stakes spike.

From intent to deploy, one thread: measure constraints, ship with margins, iterate like an engineer at the pit wall, not like a sprint in chaos.

Experience

Two real jobs, not a capability brochure.

Truestack first: full-stack ownership in production-shaped work. Before that, ELVTD: immersive web, client delivery, part-time intensity.

Current · Full stack developer

Truestack Technologies

Full stack, with the boring parts taken seriously.

I ship features across UI, services, and the small infra decisions that keep releases calm. The context is production-shaped: move carefully where it matters, move clearly everywhere.

Across the stack
From the shape of data to the shape of screens: one person keeping the thread so nothing hides in the handoff gap.
Under constraints
Correctness and traceability where the domain demands it, not polish swapped for rigor.
Through to delivery
Implementation to release: pairing when it helps, notes when the next reader needs them.

Previous · Full stack developer · Part-time

ELVTD

Client work where the screen had to feel dimensional.

Part-time on a shipped client build: heavy Three.js and motion, inside a team that still had APIs and deadlines. The job was to make the visual layer believable and performant, not just pretty.

Three.js & motion
Scenes that read well without tanking the frame, balancing budget, readability, and what actually goes live.
Client rhythm
Someone else’s brand and timeline: scope you negotiate, then finish.
Stack in context
Frontend with backend in the room. No UI that pretends data and auth aren’t real.

Proof over work

Four builds. One still on the grid.

Scroll each build — linger on the screens, then move on.

Scroll — panels reveal

01 / 04

Orders, kitchen, admin in one system

Food Ordering System

Full-stack ordering with menus that don’t break under change, operator tools that stay clear, and flows built for real traffic, not demo day.

Order · kitchen · admin: 3 surfaces
One system, not three demos: Full-stack

Customer-facing menu and checkout flow in the food ordering system — Customer flow — browse, cart, and checkout tuned for mobile-first ordering.

Kitchen and admin dashboard views for the food ordering system — Operator view — kitchen queue and admin controls in one cohesive surface.

Scroll — panels reveal

02 / 04

Suggestions and spots near you

AI Food Planner

AI-assisted food discovery — get meal suggestions tailored to your taste, then find restaurants nearby without jumping between apps or chat threads.

Food suggestions on demand: AI assist
Local restaurant discovery: Near you

AI food planner home with meal suggestions and nearby restaurant discovery — Discovery surface — AI meal suggestions and nearby spots in one calm, product-first layout.

AI-assisted food recommendations and nearby restaurant results — Assist layer — refined suggestions and local restaurant picks when you’re ready to decide.

Scroll — panels reveal

03 / 04

Counter speed, back-office clarity

POS System

Point-of-sale built for real shifts — fast ticket flow at the register, inventory and reporting that stay readable when the lunch rush hits.

Register · orders · catalog · stock · reports: 5 surfaces
Built for rush-hour throughput: Shift-ready

POS register and checkout screen — Register — ticket flow tuned for speed during service hours.

POS order management and line items view — Orders — line items, modifiers, and totals without hunting through menus.

POS product and menu catalog management — Catalog — products and pricing structured for staff who update menus often.

POS inventory or stock management screen — Inventory — stock levels visible where operators need them, not buried in admin.

POS reports and analytics dashboard — Reports — shift summaries and sales readouts for closing the day.

04 / 04

Every angle. One calm screen.

F1 Multiview Watch Tool

A multiview race companion — stack onboard feeds, timing, and track context in layouts you control, without losing the lap when the action splits across channels.

Custom feed layouts: Multiview
Built for live sessions: Race pace

Coming soon

Onboard

Track

Timing

Battle

Multiview layout — in build

Principles

How I judge good work.

Velocity

Move fast, but stay legible and quality.

Control

Systems should stay understandable under pressure.

Craft

Interfaces are engineered, not decorated.

Consistency

Everything ships at a high standard — from structure to polish.

Personal

Beyond the pit wall

What keeps the standard honest when no one's logging in: discipline away from the desk, making things with my hands, and moving when the screen finally blurs.

Racing mindset

Precision under pressure

Racing rewards prep and restraint. The same instinct I bring to systems: measure twice, ship clean, and never confuse chaos for speed.

Creative side

Guitar and building

Fingerpicking clears my head the way a careful refactor does. I build off-screen too: small projects, real materials, patience over trends.

Balance

Sports and movement

Training is a reset: teamwork without Slack, progress you can’t fake. It keeps ambition from eating the rest of life.

Loading sequence

Driven With Purpose

I love speed, systems, and the pursuit of precision.

Formula 1 reminds me that performance is never accidental. It takes discipline, pressure, and consistency.

That same mindset shapes how I build products, solve problems, and grow as a developer.

But beyond performance, I also care about purpose.

Anchored beyond the build. Purpose that outlasts any sprint.

Not every system behaves the way I expect, and not every solution is clear from the start. I’ve learned to build with conviction, but not assumption. To stay open, to adjust, and to trust the process even when the path isn’t obvious.

Proverbs 3:5

Every build comes with iterations. Bugs, failures, and rewrites are part of the process, not the identity. What matters is the ability to move forward, refine, and keep building without being defined by a single version.

Romans 8:1

Systems don’t always fail quietly. When things break, it rarely happens in isolation. It cascades, pressures rise, and clarity matters most. I’ve learned to stay steady in those moments: not reactive, not rushed, just focused on restoring control and moving forward with intention.

Mark 4:39

Let's build the next launch.

Tell me what needs to ship. I'll bring telemetry-level clarity, race-pace delivery, and a calm pit-wall process.

Inspired by andrewreff.com