Photo: free stock photography (Unsplash licence) — see imprint
Where types earn their keep
At the boundaries: what comes out of the ERP, what goes into the payment provider, what the shop sends you. A wrong shape at a boundary is the bug that silently charges the wrong VAT rate for a month. Types catch it at compile time.
`any` is a decision, not an accident
A codebase with `any` sprinkled through it has all the ceremony of TypeScript and none of the safety. Turn on strict mode from day one — retrofitting it into a 40,000-line project is a project of its own.
Validate at runtime anyway
TypeScript disappears at runtime. The ERP that promised you a number will one day send you the string "12,50". Parse and validate external input with a schema validator — types are a design tool, not a guard.
The real payoff comes in year two
Types pay back when someone who did not write the code has to change it under time pressure. That is the whole business case, and it is a good one.
- Strict mode from line one.
- Types at compile time, validation at runtime.
- The payoff is maintenance, not fewer bugs today.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer