41–50 of 114 posts
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.
Err, that is complete nonsense. If there is a reasonable case to be made then people should consider it.
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…
NOTE to developers: This is why you shouldn't accept PayPal!
> "...the framework was not utilized correctly which resulted in the numerous bugs and browser incompatibility issues." 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, metho…
I think you just pointed what the problem might've actually been: Not using the framework to prevent browser incompatibility. The OP didn't say that CakePHP was the cause of the problem.
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…
This is not a given, and it's why we have contracts. I've certainly never worked one that was refundable, but you never know.
> Everyone who evaluated the code said the same thing, to sum it up (in their professorial opinion) the framework was not utilized correctly which resulted in the numerous bugs and browser incompatibility issues. How using PHP framework may result in browser incompatibility issues? Whole processing happens in the server side for PHP, not in browser...
On the other hand I would like to say that it's good to open the discussion instead of, like most companies would, not responding and letting the legal team handle anything if necessary.
That's all, carry on. I hope everyone's bickering and finger-pointing goes well on this fine Friday.
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.
But he should say (if true) that they threw out the old code because of reasons, and rewrote it from scratch.
That was the biggest issue raised in the initial allegation: that they were currently using code that they had not paid for.
Typically in a contract relationship you have alot less obligations than hiring a salaried employee. At the same time, this person is using their valuable time towards your project. As a result of this, they usually ask for compensation which is agreed upon beforehand.
You agreed to a certain amount of compensation, and than chose not to pay. Sometimes contractors do not meet expectation, and I've seen this happen. But if you have already agreed upon milestones it is only appropriate to pay them at least up to the point at which you request they quit or fire them.
If you did not agree upon milestones (which a business with your funding should have.) You should still be paying him for the work done. Your disagreement over his work could cause his family to go hungry for a week. Such is the life of a contractor.
All in all, perhaps both of you performed without much regard to ethic. He did a shoddy job and you refused to pay. But your running the business and as a result have a lot more to lose from a bad image.
Just pay up and move on.