[flamebreath447]

Ruby code based that I’ve worked on that were a mess had nothing to do with review or guidance and everything to do with delivering as quickly as possible.

It’s inherently a part of Ruby, a feature one might say, that you can probably spin up a full functioning web application from Front End to Database in hours. This type of speed setup and launch inhibits not even thinking through design principles or other people coming back to read or work on the code.

Furthermore, because everything can be an object you end up writing boiler plate checks for nil values all over the place or don’t and ignore those cases that later crash the entire process running.

Most of these issues are not prevalent in strongly typed languages because, other than custom objects, what you define is what you get.

If speed is your only priority, say a startup, I would never just go throwing untyped Ruby code around because it’s gonna cost you in the long run trying to get others to work on your code.

[ch4s3]

I agree that in a lot of cases, moving fast is what causes the mess, and I see that as a tradeoff sometimes.

I've written a LOT of ruby over the years, and honestly bugs related to objects being the wrong type were in the minority. Yes, something popping up as nil in a weird place did happen, but not that often and it's usually easy to fix.

[flamebreath447]

Also I’ll always hate ActiveAdmin for the rest of my life.