> I also recognize that I'm very clearly a static typing snob Honestly I'm right with you. I was complaining in another ruby thread [0] the other day about how

> I also recognize that I'm very clearly a static typing snob Honestly I'm right with you. I was complaining in another ruby thread [0] the other day about how opaque ruby is in terms of context around what's actually happening and where things come from in a given block of code. I'm about a year into working at a Rails shop and it's been a wild ride coming from a background of Swift/C++/Python. There's some cool syntax niceties in Ruby around writing functional blocks which I really like, but beyond that I find myself just endlessly frustrated with it as a tool. A lot of the senior folk at my org swear by ruby and know enough of Rails to have a good intuition about what's going on and how the system is organized, but for someone new to the whole enchilada it's so hard to find mental purchase in any given chunk of code. > "if it runs, then it must be correct" this has described the root of so many of the bugs I've had to chase down, holy crap. [0]: https://news.ycombinator.com/item?id=37939011 https://news.ycombinator.com/item?id=37939011