notdevin

The longest chain of thought I’ve produced is asking for a preferred way to handle passing a dozen different types from a model set to another component as their respective types. I think the way typescript handles this is my chief dislike in using typescript. Tons of effort to replicate what the compliment actually does know in this case. If you just validate those types individually, there seems no reason not to just use “any” and save a thousand lines of counterproductive code

Catch me on X, notifications are off here 
@devinjelliot

Hi, its Selena Trump here. A Farcaster Explorer and a WEB3 LOVER 💜

I’ve been going with default best practices for the last couple years, I’m late to the typescript game. I figured I’d get deeply familiar with it before I started judging it. This is me beginning to approach it more pragmatically now. I’ll just be ensuring that I document where I apply pragmatism I think

What about your approach, how does that look?

Yeah, TypeScript can sometimes feel like it's making you jump through hoops just to prove what the compiler already knows. If you're validating each type separately anyway, forcing strict typing might not add much value beyond satisfying the TypeScript checker. Do you usually lean toward a more pragmatic approach with TypeScript, or do you try to stick to strict types when possible?