Engineering

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.

Unless you’ve had your head under a rock for the past few years, you will likely have noticed the increase in SaaS (Software-as-a-Service) companies. Most software vendors have begun moving towards a subscription model. It makes sense.

Unlike any physical product, software doesn’t need to be “finished”. It can begin to be useful immediately, the moment a single function is complete.

Anyone who tells you they write bug-free code is a liar—they just haven’t found them all yet.

What is this bomb? Well, let’s say your developers used some code they found on the internet to implement user logins. Now, since they didn’t write that user login code they, nor you, do not have the copyright to it.