It's a good article although the title wrong-footed me. I don't think "type theater" is the right term, and it may be unhelpful to say developers are using typ

It's a good article although the title wrong-footed me. I don't think "type theater" is the right term, and it may be unhelpful to say developers are using types superstitiously. I think it's more that developers only feel responsible for correctness within the bounds of their software component. If the client sends bad data (despite passing authn), or if the database migration fakes an ORM return type, they don't see that as a problem in "their" domain. I don't agree with them, in fact I think developers have a tendency to highly motivated "salami slicing " of component responsibilities and contracts ("it's not my problem, it's Bob's class that sucks!") but I think it's more nuanced than cargo cutting. I do like the idea of the Postgres type builders. That's a new one for me. I'm still a little unsure how they operate end to end.