3 ms·
>The developer bears at least a little responsibility for submitting a bid that is too low to cover successfully completing the project. I didn't say he doesn'
by macspoofing 13y ago
>The developer bears at least a little responsibility for submitting a bid that is too low to cover successfully completing the project.
I didn't say he doesn't.
The guy talked the developer down to an $800 fee, and then his interpretation of the agreement was the developer should take his feedback into account after the code was submitted to him ("I figured some graphics changes would be OK. Basically, the overlay graphics are slightly different. Same functionality"). That's definitely a self-serving interpretation. Clearly the dev does not want to do anything more than he absolutely needs to do. For that amount of money, he wants to knock-out an app in minimal time and move on.
So I'm saying they both nickel-and-dimed each other. I'm not judging, but that's what happened, and I have slightly more empathy for the developer in this case.
- eli 13y agoSure, fair enough, but roughly zero projects are going to succeed with that sort of minimal approach. It almost guarantees the client will have to pay for additional work. I was only being slightly facetious, though -- the system really does suck and I think deserves most of the blame.
- moneyrich4 13y agoalmost all software requires more additional development after its done.
- ojbyrne 13y agoAlso this is written from his perspective. It's most likely he forgot (or deliberately didn't mention in this article) everything the developer said during those negotiations, presumably things like "we will have to negotiate additional charges for anything not specifically mentioned in the spec."