"When Qurve got involved with the Charm project the site was being alpha tested by a handful of early adopters, but a months away from being ready for public consumption. Qurve was brought on in a Ruby on Rails development role to help fix bugs, complete the necessary functionality and ensure the necessary code quality for a public launch.
Over the next few months our role expanded to include a complete rewrite of the user interface, a reimplementation of the credit card billing processor and a few more major changes."
Yes, Daniel helped us backport to Rails 2.x and make a lot of improvements while we were at it, after everybody had given up on finding our Rails 3.x performance problems.
Comments
"When Qurve got involved with the Charm project the site was being alpha tested by a handful of early adopters, but a months away from being ready for public consumption. Qurve was brought on in a Ruby on Rails development role to help fix bugs, complete the necessary functionality and ensure the necessary code quality for a public launch.
Over the next few months our role expanded to include a complete rewrite of the user interface, a reimplementation of the credit card billing processor and a few more major changes."
http://www.qurve.com/clients/charm/
Yes, Daniel helped us backport to Rails 2.x and make a lot of improvements while we were at it, after everybody had given up on finding our Rails 3.x performance problems.