The TypeScript keyword I see misused most is as. Most of the time the author wanted satisfies, which checks the shape and keeps the narrow type.
What as actually does
Every as SomeType tells the compiler to stop checking that expression. Sometimes you need that. Usually you don't.
type Config = { port: number; host: string };
// Compiles fine, even though host is missing
const a = { port: 3000 } as Config;
// Error: property 'host' is missing
const b = { port: 3000 } satisfies Config;What satisfies gives you
satisfies validates the value against the type and leaves the inferred type alone. You get the check, and you keep the precise literal types instead of widening everything to the annotation.
const routes = {
home: "/",
blog: "/blog",
} satisfies Record<string, string>;
routes.home; // still known to exist, typed as stringThe rule I give my team
If you write as, add a comment explaining why the compiler is wrong. If you can't write that comment, the compiler isn't wrong.
The codebase got noticeably safer once we started enforcing that one habit in review.
Building something like this?
I'm Ahmed Mamdouh, a senior full-stack and AI engineer. I reply within one working day.

Scaling 100k WebSocket connections: the reconnect storm
At 100k+ concurrent sockets the count is easy. The reconnect storm is what breaks, and jittered backoff, load shedding and resumable sessions fix it.

npm v12 blocks install scripts by default
npm v12 no longer runs preinstall, install or postinstall scripts unless you approve them, closing a common supply chain attack path.

Node.js moves to one major release a year
From Node 27, Node.js ships one major a year and every release becomes LTS, ending the odd/even split most teams already ignored.
