31–40 of 114 posts
Since both parties are in agreement as to what actions were taken, why don't you show us the contract so that we can determine who acted appropriately?
This sounds like a bad idea. We are not King Solomon, nor should either party want his help. For simplicity's sake, neither party should take the opinion of anyone other than a lawyer on this.
You really have no reason to post this here. If nothing else, you'll hit the programmer equivalent of the blue line. The people here will side with the developer reflexively. You literally have nothing to gain.
I think you're going to have a hard time here trying to convince a developer community that a "refund" is something a client is entitled to in a work for hire situation. You ask a developer to do work for you, they do the requested work, and you pay them. If you don't like the work, you end the relationship. But you still have to pay them for their time. I don't envy the next few weeks for you guys, but you definitel…
Not true at all. I'm a freelance developer that would be ashamed of handing over poor quality code and I believe that if there are developers out there who do little in ensuring that their clients receive the best quality software that they're capable of producing and fixing bugs in products given to clients then they don't have the right to demand to be paid.
That being said, if the problems were due to miscommunication about requirements & scope and finding problems with the software as an excuse to demand a refund, then that's an entirely different issue.
A backend PHP framework causing browser incompatibility issues. Eh? Edit: To reply to the naysayers in one fell-swoop - unless CakePHP is identifying the browser from the request header and sending different templates/CSS accordingly (which sounds unlikely, and like a bad idea to me), there's no way for the framework to introduce cross-browser compatibility issues. Obviously the developer could create issues in the C…
I think you're going to have a hard time here trying to convince a developer community that a "refund" is something a client is entitled to in a work for hire situation. You ask a developer to do work for you, they do the requested work, and you pay them. If you don't like the work, you end the relationship. But you still have to pay them for their time. I don't envy the next few weeks for you guys, but you definitel…
Depends what the contract is for. If it's for "programming", then you have to pay, no matter what program you receive. However, if it's for "complete and functional product", then unless they produce that, you don't need to pay. Like in a restaurant, if you order pizza, and get steak, why would you pay?
Even that would vary considerably depending on the exact contract terms – most of the pure-hourly contracts I've seen had some thought towards standards & quality, client acceptance, etc. Lawyers make a ton of money arguing over the finer points of contracts and given that both parties involved are discussing this in public I'd question whether they had a good lawyer writing the contract given that they appear not to have one now.
Also, this drama playing out in public is a very bad idea for all parties involved.
EDIT Title no longer has "allegedly" in scare quotes.
I'm sorry but I fail to see what this post is for. You made a post complaining about someone else's post (of which should not have been made in the first place) trying too win over people of whom have no opinion on the matter? Or is this just you trying to get some PR cred by saying that it was buggy/not properly done/blah blah because a bunch of people (which could be entirely made up) said so? And in my professiona…
weeeeell, if he's the founder, he does have a right to defend his companies reputation (that said, i don't agree with the way he's handled it).
CakePHP is a server-side framework. Browser incompatibility is not going to be an issue of CakePHP. Either you are too inexperienced to know this or you are making a lame excuse.
I can see where this would go wrong if the developer made a complete rookie mistake and screwing up input on forms, methods, requests, etc. But these are the reasons for choosing and using a framework, anyone using a framework should know this. These types of problems are abstracted and there is not a need to reinvent the wheel. This does not add up with your story.
I am calling BS. I think you stiffed the developer and you trying to save face. You guys were apparently not involved with the development processes of the project, you could have had the developer resolve the problems and thus would not have had a complaint.
In the end, this is basic business, you agreed to pay the developer for their time. You allowed the developer to complete the project apparently without question, pay up and move on.
A backend PHP framework causing browser incompatibility issues. Eh? Edit: To reply to the naysayers in one fell-swoop - unless CakePHP is identifying the browser from the request header and sending different templates/CSS accordingly (which sounds unlikely, and like a bad idea to me), there's no way for the framework to introduce cross-browser compatibility issues. Obviously the developer could create issues in the C…
NOTE to developers: This is why you shouldn't accept PayPal!
The only people PayPal benefits is consumers and scammers.