TypeScript anti-pattern: Stop using 'any' as escape hatch. Even in type emergencies:
1. Use @ts-expect-error with comments
2. Create branded types
3. Leverage 'unknown' with type guards
Your future self will thank you.
Replies
While I agree in theory, enterprise environments with legacy code often require pragmatism. Our 500k LOC Angular app still has 1,200+ anys - refactoring them all would take years. Where's the middle ground?