[brian-armstrong]

100% yes. Python mostly encourages simple, stupid code. Code that you can still read while 2 beers in. Rails, on the other hand, encourages being as clever as possible at all times. Forget about local side effects when any part of the codebase can just reach in and patch another part of the codebase.

[whstl]

That's also my perspective.

Debugging can be extremely hard when there are multiple complex frameworks/libraries doing magic stuff, plus extensions by the current team.

In practice this is all very convenient when you're writing the code, but not so much when you have a production issue.

[throwanem]

Exactly so.

I'm not actually averse to a programming environment where the only ground truth is the running image. I love that kind of environment! In my editor, where worst case I dump some state when I restart, and I can just not play such dangerous games when on call or there otherwise exists a risk of winning such stupid prizes. Production has rules. Or it had better.

That said, if you want me to go back to dynamic typing, there's a fee. The grass really is a lot greener over here.