3 ms·
> That's precisely the problem. If engineers were a dime a dozen, then Rails could be a great choice. If engineers are hard to find then isn't using a framewor
by wlll 4y ago
> That's precisely the problem. If engineers were a dime a dozen, then Rails could be a great choice.
If engineers are hard to find then isn't using a framework that maximises developer productivity the way to go? Rails definitely falls into that category.
Related, we recently advertised for Rails and React engineers. We had about the same number of applicants for each position but the Rails engineer quality was in general higher than the React engineer quality.
- solatic 4y ago> If engineers are hard to find then isn't using a framework that maximises developer productivity the way to go? Rails definitely falls into that category. Languages are not like cars. You cannot take a professional Rust engineer and drop him into a Ruby environment and expect him to be immediately highly productive, as if you were switching him from a Miata to a Ferrari. Languages need to be learned all over again, their ecosystem needs to be learned, beginner code needs to be reviewed by someone senior who is more familiar with the language. You can't just make an executive decision to go with Ruby because it has a reputation for productivity and expect immediate productivity gains.