Developer-Experience

This is the fourth post of Building a Minimalist Task Manager series part 1 - Why TypeScript Might Be Too Much for Your Project part 2 - The TypeScript Trade-offs No One Talks About part 3 - JavaScript Is Loose for a Reason — Should We Be Tightening It? Ever notice how TypeScript developers sound like they’ve joined a cult? They don’t just use TypeScript—they evangelize it. They don’t just write types—they architect elaborate type hierarchies that would make a database administrator weep with joy. They don’t just catch bugs—they prevent entire categories of human thought that might lead to bugs. ...

This is the second post of Building a Minimalist Task Manager series part 1 - Why TypeScript Might Be Too Much for Your Project part 3 - JavaScript Is Loose for a Reason — Should We Be Tightening It? part 4 - TypeScript: Strong Types, Strong Opinions TypeScript has one hell of a PR team. Every conference talk, every blog post, every Twitter thread paints it as the silver bullet that will save us from JavaScript’s chaos. “Catch errors at compile time!” “Better IDE support!” “Safer refactoring!” ...

You know that feeling when you’re browsing through a new framework’s documentation, and it starts off promising. Clean syntax, great performance, awesome community support. Then you hit the setup guide, and suddenly you’re reading something that sounds like a Terms of Service agreement written by a particularly possessive ex: “To use FrameworkX, you must use our build tool, our linter, our testing framework, our deployment pipeline, our code formatter, and also please consider naming your firstborn child after our mascot.” ...