1. 3 ways to approach a Ruby on Rails application upgrade

    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. On top of that, never prioritising an upgrade means that you’ll find it […]

    Read the article →
  2. 3 actions you should take if your Ruby on Rails application has been around for more than 3 years

    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.

    Read the article →
  3. 6 things you must back up on your web application

    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.

    Read the article →
  4. Using SaaS software vs creating your own bespoke software

    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.

    Read the article →
  5. The murky world of legally decompiling software

    As we’ve discussed before, having the source code is crucial to be able to make further changes or fix bugs to your application. It is also a huge timesaver to understand the current logic and data structures that need to be transferred to a new platform.

    Read the article →
  6. Do you have a quality strategy for your software?

    “We build good quality software!” – says every software developer.

    Read the article →
  7. Software isn’t static

    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.

    Read the article →
  8. Bug fixes aren’t free

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

    Read the article →
  9. Did your developers just build a time-bomb into your bespoke software?

    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.

    Read the article →