ReactUp #9, Gdańsk
Static typing is often sold as taste, syntax, or personal preference, but this talk treats it as practical feedback for JavaScript applications. It starts from the everyday risk of dynamic code: data crosses boundaries, assumptions drift, and many mistakes are only discovered once a path runs in the browser or in production.
The presentation explains what static type analysis can and cannot promise, then looks at tools and adoption paths familiar to JavaScript teams, including Flow and TypeScript-style gradual typing. The focus is not on making every annotation perfect, but on making the important contracts visible at module, API, and component boundaries.
For larger products, the value is shared confidence. Typed data models, explicit function shapes, and checked integration points help teams catch mistakes earlier, review changes with more context, and scale ownership as the codebase and number of contributors grow.