[phplovesong]

> Okay, so you are dreaming of a situation where you allow a new developer who doesn't know anything about how to engineer software unfettered access to your codebase and he goes in and starts mucking about to where he ends up doing things that no sensible human would ever consider acceptable?

Tell me without telling me you have never worked on a large scale business app.

[9rx]

I did long enough to know that in large teams you won't find many accepting of usable type systems. For the same reason the blub developer cannot write good tests, if they can figure out how to write tests at all, they equally fail with types. Which makes sense — testing and types try to solve the exact same problem. The mindset required to grasp and be productive with both is identical. So your imagined hypothetical doesn't even work there. These large scale apps of which you are speak are simply built around constant failure in production. If it is good enough for GitHub...

The only place where the your contrived idea is in any way plausible is where you have a solo developer who thinks he is able to write code without making mistakes or needing to document anything, using a half-assed type system not failing as some kind of proof to himself of that. But in reading this he, unless the hubris is completely off the charts, will be reevaluating that stance.

[phplovesong]

> you won't find many accepting of usable type systems

I think its not about the "typesystem" but the fear of using something the dev is unfamiliar with. I know people who has written the same code, in the same language for 20+ years. "It worked then, and it will work now" is tattooed on their forehead. Its basic human behaviour, you see this in politics, business and life in general.

> testing and types try to solve the exact same problem

Sure, they overlap.

Tests are just a poor mans types, Types are just a poor mans tests

But in my mind tests cover the how, and types the what. With both you need less of both. Its a win-win.

> These large scale apps of which you are speak are simply built around constant failure in production.

This is true. But im going to my grave trying to change that. Its an uphill battle.