I Stopped Throwing Errors and My Code Finally Works - Andrej Acevski

JavaScript error handling is a mess. Promise.reject() fails silently. try/catch nests seven levels deep. TypeScript gives up at the first async boundary. And we've just... accepted this? For years? This talk has three parts: Part 1: The Roast (therapeutic): JavaScript error handling is what happens when you give developers footguns and call it "flexibility." We've normalized chaos and wondered why everything catches fire. Part 2: The Discovery (enlightening): Enter Effect - a TypeScript library that starts with "what if errors were trackable?" and then keeps going. Dependency injection. Observability. Retries. Streaming. Concurrency. Schema validation. At some point I stopped reading the docs and started experiencing emotions. Part 3: The Demo (inevitable questioning): I'll show you what building with Effect actually looks like - errors TypeScript can track, retries in 3 lines, built-in observability. Then we'll talk about whether this is genius or overkill. Spoiler: it might be both. This isn't "rewrite your app" evangelism. It's "holy shit, JavaScript is missing so much" realization. No functional programming PhD required. Just curiosity and a tolerance for hot takes. 🍻