[lbriner]

I think the premise falls down with the example given about programming languages because in engineering everything is a trade-off. Cobol is not Go and would have made design choices based on not just Instituional Knowledge (or lack of it) but also because of the world at that time, the reality of hardware and software etc.

Sure, GoLang could learn something like "don't make things nullable" but it would be easy to say, "yes I know that, but in our case, this creates a benefit because of X"

Just like people who believe in TDD, DDD etc. they might all work, but that doesn't mean they are objectively the best way to do things in all circumstances.

I think the better target is learning how to think and analyze more effectively so we know what we are trading off more clearly.