Ugh. I have hardly any type problems in my Ruby code. I&#x27;ve gotten very good at recognizing implicit state and capturing it in a properly instantiated object with a well-named class. I daresay that if you don&#x27;t have this skill, a type system isn&#x27;t going to help you much and you&#x27;re going to get nasty bugs anyway.<p>The problem in Ruby is nils, and you&#x27;d have the same problem with the same solution in a static language; creation of a duck type. You can&#x27;t get away from duck types, whether it&#x27;s a maybe type or whether you perform nil-checking at the earliest possible opportunity. You learn with time and experience how to deal with inconsistent data. Ruby gives me the flexibility to do it without a lot of boilerplate.