0x00 // BINARY

I read meaning
out of raw bytes.

Full-stack TypeScript developer working in a niche most developers avoid: automotive ECU firmware and proprietary binary formats — plus the production APIs and apps around them.

0x20 // CAPABILITIES

What I build

Deep specialization in binary work, wrapped in the full stack needed to ship it as a real product — not a prototype.

[ 0x01 ]

Binary parsing

Hex-level structure mapping, checksum handling, and reverse engineering of proprietary or undocumented file formats.

[ 0x02 ]

Backends & APIs

Node.js / TypeScript on Fastify, Knex & Prisma, MySQL / PostgreSQL, Redis — validated inputs, rate limiting, tested.

[ 0x03 ]

Frontends

Next.js and React, internationalized (9 languages in production), Tailwind — polished, responsive interfaces.

[ 0x04 ]

Desktop

Electron applications that talk to real hardware, including USB dongle integration and native bridges.

[ 0x05 ]

API security

HMAC request signing, replay protection, per-user quota systems, and standardized error handling on every route.

[ 0x06 ]

Reverse engineering

Given only sample files, I map the layout — offsets, records, encodings, checksums — and turn it into typed code.

0x40 // THE PIPELINE

From uploaded binary to flash-ready file

The production SaaS I designed and run for the automotive chiptuning industry — every stage built, secured, and shipped by me.

01

Upload

2–8 MB ECU firmware in via web UI or HMAC-signed B2B API.

02

Fingerprint

Signature scan identifies ECU family and software version.

03

Detect

Hex-level location of diagnostic trouble code tables.

04

Patch

Changes applied in place; checksums recalculated.

05

Deliver

Flash-ready file returned, with per-user audit trail.

0x60 // PROOF

Running in production

95+ECU types supported
<5stypical turnaround
2–8MBbinaries parsed
9UI languages shipped
DTC management interface parsed from ECU firmware, showing SPN/FMI-decoded fault codes
// fault codes parsed directly from the firmware binary
0x80 // CONTACT

Got a format that needs to
work exactly right?

Binary parsers, APIs, or a full-stack build. Send me a few sample files and what you need out of them — I'll confirm feasibility before you commit.

fethan.us [at] gmail [dot] com