Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Questions to other freelances out there.
I suppose it's a common occurrence to be involved in some project, asked to add some feature or modify something, and then looking at the source and find an unmanageable burning mess.
If upon such a discovery you decide you're not taking the job - for example, given the situation you need to charge quite a lot more and the customer cannot pay the appropriate amount - how do you go on explaining your reasons?
You just go out directly telling them about the dire situation of their codebase? Try to find a nice way of telling the truth? Make some excuse (cannot because personal reasons)?