I recommend learning static typed languages first, maybe even working in a large code base. Then you will truly appreciate the ambiguity of dynamic languages an

I recommend learning static typed languages first, maybe even working in a large code base. Then you will truly appreciate the ambiguity of dynamic languages and look at them less like “baby languages”. In app code bases, there are always multiple duplicates of the same type, no one truly respects reusability partially because it’s not always practical. With dynamic typing, you can be completely transparent and have multiple “Car” classes. It doesn’t matter because types don’t matter. To us they both represent a car, no need for converters, helpers etc. Car1 definition has some method you need for Car2? No problem, just tack it on in that scope! It’s not polluting the definition of Car2, it's not going anywhere.