HomeTechnologyTypeScript

TypeScript in use

TypeScript in strict mode, on both sides of the interface. Types that only hold in the editor and mean something else at runtime are worse than none — which is why validation happens at the boundary.

Full-stack development3 case studies

A steel inspection gate standing alone on the hangar floor, one plate with a precisely cut opening in it, a man seen from behind guiding a part into the cutAI-generated
The shape is settled before the part ever reaches it.

Proven by

3 published projects with TypeScript — each with stack, role and result.

What that means in practice

Strict mode on both sides of the interface, and the types are not decoration: routes, addresses and message keys are typed so a renamed path breaks the build instead of quietly serving a 404. At the boundary — form, API, database — it is checked at runtime as well, because a type there is only a claim.

  • Strict types from the form to the database

  • Generics & Advanced Type Patterns

  • Zod Schema Validation

  • Fullstack TypeScript (Frontend + Backend)

A roller table crossing the hangar carrying identical parts, one fixed gauge above it with a part seated in it right nowAI-generated
It runs — and every part goes through the same shape
A drafting board in the hangar, a sheet on it carrying a technical profile, one dimension struck out and re-drawn tighter beside itAI-generated
The tolerance you pull tighter after the first deploy
A warped part sitting loose inside a template opening far too large for it, and beside it, unused, the plate whose opening would have fitted exactlyAI-generated
The opening cut so wide that everything passes

Other technologies

Contact

Half a minute, and you know more.

Half a minute on what I work on and how. If a question is left, write to me — an answer within one working day.