I've been up to some new and exciting things.
In the years that I’ve been a professional programmer, I’ve had quite a few chances to speak with business owners who have wanted a fixed-price bid on their projects. (That’s where you ask your developer to tell you how much something is going to cost to build, and then regardless of how long it takes / what goes into the project, that’s what you pay him or her.)
In 2012, I wrote this list of 'skill-testing' questions for what you ought to know before starting Rails. I still think they're relevant today, even if I don't use Rails that frequently. These are good things to know, but they're the bare minimum.
Rails is a framework not only comprised of a series of substantial components, but also dependent on non-trivial technologies to enable the productivity and happiness gains that veteran programmers often see. Most complaints about the framework bely the nature of the problem, which is that beginners are underprepared for introduction to the advanced concepts inherent in Rails, resulting in vocabulary confusion. Furthermore, this is a feature, not a bug; Rails's value comes with its complication, and attempts to simplify it to be more beginner-friendly are simply misinterpreting the problem.