Domain modelling
Represent meaningful states and identifiers so invalid combinations become harder to express.
TechnologyTypeScript Software Engineering
Where it mattersFull-stack web products
Type-safe product development
TypeScript Software Engineering
TypeScript creates leverage when types express domain truth and boundaries, not when annotations merely repeat obvious implementation details.
How we use it
A technology choice is useful only when it improves the product or its operation.
We use TypeScript to make data shapes, permitted states, service contracts, and refactoring consequences visible before runtime. Runtime validation remains essential wherever information crosses a trust boundary.
Architecture decisions
Trust boundaries
Validate external input at runtime instead of assuming a compile-time type makes data safe.
TechnologyTypeScript Software Engineering
Where it mattersShared API contracts
Contract ownership
Choose how API, event, and database contracts are generated, versioned, and reviewed.
TechnologyTypeScript Software Engineering
Where it mattersWorkflow engines
Strictness
Use strict compiler settings and address uncertainty deliberately rather than hiding it with broad casts.
TechnologyTypeScript Software Engineering
Where it mattersFinancial and operational systems
Where it fits
01—
Full-stack web products
02—
Shared API contracts
03—
Workflow engines
04—
Financial and operational systems
05—
Reusable component libraries
06—
Large codebase modernization
Engineering choices