The Ruby on Rails framework is used by numerous organisations to create everything from relatively simple sites to internationally recognisable platforms.
Perhaps the question should really be – what can’t you make with the Ruby programming language on the Rails web application framework?
When you add code to your codebase, you are assuming responsibility for it. When you use a third-party dependency, you’re effectively assuming liability for code you did not write.
From a support and maintenance perspective there are some standout features/improvements that we’re excited to see.
By that definition, every programmer is a Mender. But as we’ve seen, some people identify themselves differently.
As developers, there are some better practices that, if followed, will make your future life more comfortable as you continue to develop the application.
Upgrading a Rails application is almost never the top priority for a company, but over time it pays to remain up to date. You ensure that bugs and security vulnerabilities get fixed. Plus, new features make future feature development quicker and easier.
If your Ruby on Rails application has been around for more than a few years or so then here are 3 actions you should take.
Here are 6 things you should check you have covered so when the proverbial hits the fan, you’re not the one running for cover.