Allison Beckwith
Annie Cocchia
Brian Middleton
Carl Anderson
Carlos Rodriguez
Eric Williams
Gary Blessington
Jack Bouba
Joshua Bennett
Neil Mahoney
Robby Russell
Ryan GenselDevelopment
Rails Code Audit
Keep your code strong and healthy with regular checkups. Our team of expert Ruby on Rails developers are just the ones to do it. How stable is your code?
Our extensive experience working with Ruby on Rails over the past five years has provided us with the opportunity to review many applications developed by other firms and contractors. Some of these have been designed and developed to near perfection, though many, unfortunately, have suffered from bad design and/or implementation. The result of these common mistakes is increased costs for the project stakeholders, both financially and in time to market.
To help businesses discover these problems earlier, we have designed a process for auditing and analyzing Rails applications, assisting the project team at different intervals in the project lifecycle. For example, you may be only a month or two into your design and development process and would like some seasoned professionals to look over your shoulder and provide you with some feedback before moving on to the next stage. Or, perhaps you’re getting ready to launch your application to the public in the near future and are concerned about the stability of your investment.
We feel that it is in your best interest to have another set of eyes review your application and provide you with an overview of where any critical issues may lie within your product. It also allows us to advise you on how to proceed with your design and development efforts, which would be valuable to your existing team, or any other firm that may continue working on your product.
Designing your Rails Code Audit
The deliverable for the Code Audit is a documented detailed analysis of your application’s current code base, helping to answer important questions.
Best Practices
- Do we adhere to the conventions of the Rails framework?
- What is our testing framework and process?
- Do we practice the DRY principle whenever possible?
Security
- How secure is the application?
- How is privacy of personal user data handled?
Architecture
- How well is the application and data model performing?
- Is the Model-View-Controller implemented well and organized?
- Do we have a strong information architecture?
Future Planning
- Is our application scalable?
- What are the most important issues to address?
- How can we speed up our development efforts?
The 8-hour Audit
An eight hour code audit review package consists of seven hours of review and documentation by one of our experienced developers plus an hour long follow-up phone conference (or in-person meeting if you're local).
Custom audit packages are available upon request.
Starting at $2,000
We've been active members of the