Comment by jfinnery

Can confirm, I'd charge a laaaarge premium to ever work on an existing Rails codebase again.

Did it several times over a period of 15 years and they were always a wreck and unreasonably painful to work with. Every single time.

I'd start a green field one, no problem, provided I get veto on gem choices ("Let's use some twee fucking template language that's a ton worse-performing than the default and doesn't let you programmatically control nesting levels / end tags because it's terribly designed" yeah how about we don't do that because it's going to make my life a living hell) without charging a premium. But no more onboarding to rails codebases without enough money to make it worth my hating every second of work for the (assuredly short) duration.

... and I like Ruby!