Yeah, the company I work for is small and all of us are Mormons (well, 
there are two who aren't, but they're good guys) so we tend to take a 
little stricter view on things like alcohol... but make it a "Sprite 
button" and I'm right there with ya! :oD

Cheers!

Kevin Aebig wrote:
> Beer button? Complete Genius...
>
> !k
>
> -----Original Message-----
> From: Christopher Jordan [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, May 15, 2007 2:21 PM
> To: CF-Talk
> Subject: Re: OT: is this wrong on my client's part?
>
> Good Lord Mike, why on earth did you agree to this kind of arrangement 
> in the first place!? :o)
>
> I think I'd tell the client to get stuffed, but if you've already put in 
> a bunch of time on it then I think I'd triple my normal rate, and do 
> like you said and charge for each and every bug you fix.
>
> On another front, I've got pretty strict guidelines about who I'll do 
> work for (meaning what sort of business). For instance, I'd never do any 
> developing that contributed in any way to the sale of pornography. My 
> company has turned down jobs for liqueur stores, and once for a movie 
> theater that wanted us to install what amounted to a "beer button" on 
> each of the seats in their theater.
>
> What I'm saying is that I'd be *extremely* uncomfortable working for a 
> man who wouldn't let me know anything about his product or who couldn't 
> trust me to come to his location and code on his equipment.
>
> In short, I think it's your client who's being unreasonable, and you 
> just seem to be doing your best to deal with it.
>
> Cheers,
> Chris
>
> Mike Kear wrote:
>   
>> I have a client who is REALLY paranoid about access control and who
>> wants me to develop a complex shopping cart for him,   but never have
>> access to his system.   I have to submit my finished project on CD,
>> then  he'll load it up and test it and let me konw if it works.
>>
>> The site is a cluster  of two servers, "probably on windows, not sure
>> at this state", and the CF will be "probably CF7 Enterprise".    The
>> database will be definitely SQLServer2005.
>>
>> I'm not allowed to use cookies of any kind,  not allowed to use client
>> variables, not allowed to use sticky sessions, so that means i have to
>> write my own version of client variables, using UUID as url variables.
>>  Oh and new UUID has to be issued on every single page view.    The
>> shopping cart is multiple currency, has to be custom written, as does
>> everything else.
>>
>> Because he wants to own outright all the IP in the project, no
>> pre-written modules can be used.  Everything must be custom written
>> for him, so he can own all the IP.
>>
>> I built the prototype on my shared server, and it was a very
>> interesting exercise for me, writing my own version of client
>> variables, but it wasnt without anguish.  There were quite a few
>> minutes spent scratching my head figuring out how to do some of the
>> parts of the site.
>>
>> I am reluctant to deliver the site for acceptance testing without ever
>> having had the chance run the code myself on its finished environment,
>>  or even having the chance to see what the environment is.   (The
>> devil is in the detail all too often, dont you think?)
>>
>> He's going to install my code on the servers, test it,  then describe
>> to me what needs changing, or describe what's broken.  (I wont be able
>> to see the errors for myself because it will be behind firewalls at
>> that stage).   Then I'll fix the errors as described or make whatever
>> changes they request, submit the code on CD again, and they'll tell me
>> if i have fixed the problem.
>>
>> So here's my question. I dont like this arrangement at all.     And
>> i'm asking your opinion about what I should do.
>>
>> My current inclination is to deliver the code as requested, but
>> without any warranties that it will work, since I have been required
>> to build it without any means of testing it in their environment.   I
>> am thinking I'll submit my final invoice for the completion of the job
>> on an "as is" basis, and give them the CD with the code on it when i
>> get the cheque.  Then bill them for every change they want made,
>> whether bug fix or enhancement.    I figure i can get away with
>> (truthfully) saying "that might be an error on your system but it
>> works without that error on my test environment and since you denied
>> me access to your environment you will have to pay me to make a
>> change."
>>
>> Am i being unreasonable with this?
>>
>> Cheers
>> Mike Kear
>> Windsor, NSW, Australia
>> Adobe Certified Advanced ColdFusion Developer
>> AFP Webworks
>> http://afpwebworks.com
>> ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month
>>
>>
>>     
>
>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Macromedia ColdFusion MX7
Upgrade to MX7 & experience time-saving features, more productivity.
http://www.adobe.com/products/coldfusion?sdid=RVJW

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278215
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to