3 ms·
Of course, but the trouble remains what is stated in the very next sentence: > There are plenty of ways to nicely organize your code and you should probably sp
by randomdata 2y ago
Of course, but the trouble remains what is stated in the very next sentence:
> There are plenty of ways to nicely organize your code and you should probably spend more time refactoring.
Ruby/Rails makes this a time consuming process as compared to many alternatives. If you have all the time in the world, Rails is great, but for the rest of us that also have to think about productivity...
- Linell 2y agoDo you have any examples of why RoR is more time consuming to refactor than other languages?
- rapind 2y agoIMO rails is a victim of it's own success. By being incredibly productive and easy to get things up and running, you don't have to reason about your data design as much, meaning you are more likely (not guaranteed) to throw together a bunch of badly related garbage. People love to blame the language and the framework, but in reality once you're past the proof of viability point, it's usually worth taking the time to review some of those initial decisions... except now you need to GrOw! :) The fact that it's rails is irrelevant. It could be any tool that makes you really efficient by never erecting guard rails.