[ReflectedImage]

It's not really true that type safety is useful for large projects.

It's generally better to do proper micro-services.

Type safety is the inferior way of doing it where you get hit with a double whammy of long compile times and extreme code verbosity.

[zogrodea]

Network API contracts/documentation are just an attempt of type safety over the untyped network boundary.

Network communications are the most tedious and annoying part of programming for me because of the validation of the request body and checking that it has all the fields needed.

Microservices only increase the amount of documentation needed. I would prefer to lessen the amount of documentation by letting the compiler/code do the work instead.

[ReflectedImage]

No, it's forced modularity. It's saying there are hard lines between parts of your program that can't be crossed. This prevents the over time formation of spaghetti code.

It's like British tanks in WW2, your system is composed out of standard parts. Not necessary the best, but standard parts and that's what tends to be important.