As a rule, I'm a terribly impatient programmer... waiting around for minutes while an error email works it way into a bug tracker, or my inbox is simply too slow. So I decided to write a plugin for Lighthouse that would allow my application to submit bug directly to Lighthouse via a simple web service call.
I started tearing into the code and thanks to the very clean and simple way Ray wrote it, I was able to find everything I needed to setup the data input. I dropped in a custom CFC to handle the requests and everything looked good. That is until I fired off a test request to it and BAM... nothing happened.
After a fair amount of digging through the code and some google-ing, it turns out, that the onRequest function was swallowing up the web service response and basically refusing to let it back out.
As it turns out, this is a known "feature" of using Application.cfc and the onRequest method. Of course, that seems like a total cop out to me, but thankfully there is a quick and easy fix for it.
If you are planning on using onRequest in your Application.cfc, simply add the following code to your onRequestStart method.
This simple test against Arguments.thePage checks to see if the file type being called is a cfc. If it is, it dynamically deletes the onRequest method from the CFC in memory and magically lets the response through.
But silly me, it seems like this is something that should be addressed in the next CF8 updater or in CF9.
CF_Sunstroke
Randomness from Alan Rother
Upgrade Pricing on ColdFusion Builder 2
So, maybe I'm late to the game wih this, but I was just on Adobe.com and happended to look at ColdFusion Builder 2 in the store and saw they now offer upgrade pricing for Builder if you have any of the following:
Freelance Pay Scale - What should you charge
So, this started out as a bit of a brain dump on the AZCFUG.org mailing list when someone asked what the going rate is for a ColdFusion Developer these days. I recieved a lot of positive feedback on it, so I thought it might be a good idea to share on here.
A good baseline for picking a rate is:
Take what you earn a year, say, $60,000
You work about 2000 hrs a year, so your hourly rate there is about $30 an hour
Being a full time employee has it's advantages (usually..) Steady pay, health insurance, paid time off... You get the idea.
Those "benefits" have a literal value, say roughly equal to your pay.
So as a baseline number, double whatever your assumed hourly rate a full time job would be, in this case somewhere around $60 hour
I then usually add or subtract based on the job itself: Taking over someone else's evil, poorly coded project that looks like a nightmare, I add 50% - 100%
If it's something cool that I've never done before and I can learn from it, I might discount it some.
Also, factor in that you need to pay taxes on this income (we all report all of our side income, Right???) So, assume your going to lose about 40% of the money you make.
The volume of work (guaranteed work), my availability, possible perks (free stuff they make or sell), how tight or loose their deadlines are, do they seem cool or are they going to be a pain in the a**, should all factor into that pricing.
(Comments added by Cheryl Novalis-Marine)
I think you also need to consider Industry and size of the company (maybe even more so than the location). I have a long time client out of Manhattan NY, but they are a smaller company and because they are in NYC they have a lot of high expenses. No way they would be able to pay $200/hour. So, lots of things to factor in when deciding.
At the end of all of that, look at how much money you stand to take home once the job is done, is it worth the time/effort/stress
Get a FREE Blackberry Playbook (Tablet)
I'm impressed. You don't often see big companies with well established niches come around and really innovate, but RIM (Blackberry) has really done it this time.
They're getting ready to release their competitor to the iPad, the Blackberry Playbook and to make sure they have a well stocked library of apps ready they've made an incredible offer. Write an app for the Playbook, get it approved for the store and they'll send you a FREE playbook as a thank you.
