I kept trying to force the request with the following failing code:

#don't use this, it's bad
# I want to reroute /reviews to /admin
get "/admin"

That was clearly wrong, but nothing immediately jumped out at me as to how to fix it. After much googling around, I finally found the quick and easy solution:
ruby code on github here

describe "/admin" do
    before(:each){
      get :index
    }
 
    it { should route(:get, "/admin").to(:controller => :reviews, :action => :index) }
    it { should respond_with(:success) }
end

Hope this saves someone else some time.

I really hope this adds a ton of value to new or established businesses looking for more efficiencies in their web-contact-to-deal-close processes.

The plugin installs just like any other Wordpress plugin. It should be pretty intuitive to anyone that has even limited experience administrating a Wordpress site. The plugin can be downloaded from Wordpress or at my repo on github.

Fat Free CRM is a great customer relationship manager (CRM) I’ve been using for a little while now instead of Highrise. I used Highrise for a little while before I grew frustrated by its hosting costs and lack of features. The guys at 37signals don’t seem to update it very often either.

For the rails project, I forked the repository and made a few minor changes like adding access via an API key. I also added a few usability options in the view codes to make integration with the plugin seamless.

For new businesses that are just implementing a CRM solution, I’d be happy to host the CRM application on my servers for a nominal cost. Feel free to contact me for more details. (hint, the contact form is an example of the plugin in action )

To use the plugin and CRM together, just follow these simple instructions:

1. Download or clone the CRM from my github repo. Install on my servers (contact me for pricing) or on your own
2. Download and install the fat-free-crm-lead plugin either from Wordpress or my github repo
3. Configure the plugin with the URL of your CRM and an API token (details are provided in the admin interface of the plugin)
4. Watch the leads come rolling in and enjoy not having to copy and paste from emails any longer

Hopefully, this is really easy. If you run into any problems or have feature requests, please feel free to contact me.

====UPDATE====

The plugin has been accepted into the WP plugin directory. Take a look at the fat-free-crm-lead-form at Wordpress.

www.precisiontext.com

Precision Text, a brand new company with only an idea, needed to hire a solid web developer to bring their new business idea to life.  After a few conversations, we both agreed that the best way to bring this idea to the marketplace would be to use the Ruby on Rails framework and a solid text messaging API.

The application allows for business owners to gather a list of their customer’s cell phone numbers. The business can then send out a message to these customers alerting them of new deals or special offers. The response rate has been high and the utility to the business has been huge.

I built the application from scratch and within a month was comfortable with a deployment in a beta stage. Using this beta deployment, the founders put the application through some of their own testing and determined they were comfortable selling the product as it was. Within a month of deployment, they had already secured 10 contracts!

TDD

This was the first app that I built in a completely test driven development (TDD) coding style. I have had some experience with unit and functional testing, but I have never actually built an application from scratch using TDD. Even though the processes was new, I still found the coding process to be much more efficient. I will be building apps using only TDD from now on.

Daemonized Processes / Time Zones

Sometimes businesses need to send messages later than when they’re at the computer. Rather than set up a complicated cron job or some other solution, I created a daemon within the application that actively listens for queued messages and sends them according to the time the end user requested.

Implicit in the scheduling is getting their time zone right. From a usability perspective, it is much easier not to do time math when queueing a job. A restaurant owner in Colorado shouldn’t have to compute the difference of her time zone to where the server is located. Neither would she want a message to accidently go out an hour early.

For usability and business rapport reasons, I implemented automatic adjustments for the time zone the user is in. To the user, it is seamless and easy to manage.

A creative design company called Old Green Pickup began its transition to using Ruby on Rails as its primary development platform. Since this was one of only a few projects Old Green Pickup had used Ruby on Rails with, the President of Old Green Pickup hired Bryce to take over the production and make sure everything was running smoothly. This is the first project in a new relationship we wish to cultivate.

I was brought in as an associate developer to the AAA project to make sure it was completed on time with high quality. I resided in Ohio for a period of three weeks to develop alongside the lead developer.

During that time, I helped with formalizing the architectural plan of the application, offered assistance in deployment and led development projects for several areas of the application.

One fundamental role in the project was to create an online market place and integrate it with an existing SQL Server database. I also created a robust shopping cart and checkout procedure. I also built a web service to manage users in the shopping cart.

The main application was build using a Flash frontend and required data called from the Rails backend. I built a background RESTful interface and helped the lead designer integrate it with Flash.

Integration with other AAA services was also required. I built the front end code to a GIS service, a system for sending emails, and a mechanism to create, store and display unique travel products.

I returned home and continued working on the project through their successful launch in early May of 2008.

Its programming includes an interface to build medical surveys and host a variety of physician specific questionnaires. It resembles a SurveyMonkey like solution specifically tailored to the security and confidentiality concerns of the medical profession.

I developed all the code including user management and payment processing.

A “Web 2.0″ application designed as an all in one solution for medical research.

Physicians can design studies, write surveys and collaborate with peers. A unique challenge with this project was patient confidentiality. I built a secure system focused on patient anonymity.

The project also required a regular, non-intrusive, payment processing mechanism which I implemented.

A community area allows physicians to discuss emerging research and develop new studies. Includes a regularly updated blog.