@randomgeek It's like giving an 18-year-old a credit card with a very high limit when they're fresh out of their parents' house having never learned how credit works.
-
@randomgeek It's like giving an 18-year-old a credit card with a very high limit when they're fresh out of their parents' house having never learned how credit works. By the time they realize what they've done, they're in so far over their head.
-
@jamie I used Rails for exactly one project beginning to end (around version 3), and I think the credit card analogy works. You feel like you're getting bonus miles every time you use a framework feature, so you do and then the bill comes due.
I refactored heavily so it used less Rails, more Ruby. Haven't touched the framework for serious work since.
Though that's more about circumstance than anything else.
-
@randomgeek The choices that led you into those circumstances were sound, it seems.
The Rails conventions also don't scale in any direction — domain complexity, throughput, org chart size, etc. I've worked in the Shopify codebase. It looks nothing like other Rails apps and is not a model for how to work with Rails code. It only works because the company can afford to afford several entire teams working on the very specific problem of scaling Rails apps on those dimensions.
-
@jamie including "fund Rails development"
I mean it's a good thing don't get me wrong. But clearly also a hail-mary tactic for those days when throwing more staff or hardware at the problem becomes prohibitive.
