Engineering notes
Articles for people who
ship the stack
Rewrites on React, Node.js, TypeScript and AI. A translated body is shown when it exists. If it does not, you see the English text and a note that says so.
Tagged: engineering
Why Serious JavaScript Teams Adopt TypeScript
Why serious JavaScript teams move to TypeScript: types as contracts, safer refactors and editor tooling whose payoff keeps compounding as the code grows.
5 min readTypeScript does not turn weak engineering into strong engineering
TypeScript doesn't fix weak engineering. Strict type safety helps, but any, bad boundaries and untested domain rules still ship bugs. Craft beats syntax.
3 min readWho writes the code when agents join the workflow?
From autocomplete to agent swarms: map each coding agent tier to blast radius, test coverage and review gates, so humans stay on the code that really matters.
10 min read
FAQ
About these articles
Yes. Each piece is an original English rewrite prepared for this site. Structure and code examples follow the source material; prose is rewritten and checked for overlap before export.
English is the source. Another language is shown only when that translation body exists. A missing or empty translation stays in English, including on a localized URL.
New drafts land in the publish queue as they pass editorial checks. Running the site import picks up only new or changed slugs — nothing is duplicated.
Treat samples as illustrative. Validate against your stack and licences before production use. For delivery work, contact us with the brief.
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.