Type safety would change my world. Lack of it is the #1 thing causing errors for my company. You can either program defensively around it, jump through NilObjec

Type safety would change my world. Lack of it is the #1 thing causing errors for my company. You can either program defensively around it, jump through NilObject patterns (about the best option), or over-document every method which then will get stale soon to tell the intent of what's going to happen. Method chains are a trap in Rails and will always lead to NoMethodError sadness.