markmcb writes "My development team was recently pondering over a finding a practical solution to the problem that's haunted anyone who's ever used a framework: convention vs. customization. We specifically use Rails, but like most frameworks, it's great for 95% of our situations, but it's creating big bottlenecks for the other 5%. Our biggest worry isn't necessarily that we don't know how to customize, but rather that we won't have the resources to maintain whatever customize code going forward, i.e., it's quite simple to update Rails as it matures versus the alternative. What have been your experiences with this problem? Have you found any best practices to avoid digging custom holes that you can't climb out of?" Link to Original Source
This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.
Balancing Performance and Convention 0 Comments More Login /
Get More Comments