Does the client keep changing?

Question

Freelance

Kind to everyone, actually a question about a sore point .. I
started working with a customer on a Long Term (driving a regular PM who contacts with clients)
I took the first project, handed it over and after that specific changes went to everything and everything, not in terms of edits (that is, my jambs ala the calculator does not count) namely, measuring the slider into blocks, background into the video and further further further, in this regard, the project is delayed for 2 weeks, although the layout was completed in 3 days. + Of course, I began to work less because changes take 2-4 hours.
That is, the main client himself does not know what he wants, today one thing - tomorrow he saw a site with a canvas and let's do it too. How OK is that? Before that, I worked on single orders, I passed it - the customer looked - the maximum button was corrected - they fled.
I work hourly and of course the whole thing is paid. But the question is that global changes of such a plan are a hit, and the hit is not the complexity of the task itself, but the fact that one needs to be redone for another (an analogy with how if you change the foundation in a finished house, building a foundation is not a difficult task, but in a finished the house is completely different)
Of course they pay me, but I don’t want to constantly redo it, I want to do it - turn it in - and leave for a new one, and this is possible only if the customer has a clear understanding of all the wishes that the designer has implemented.
Is this a situation only for me or do you just need to endure it with clenched teeth and once they pay you can’t howl?

Answer 1

In my opinion, you just wanted to cry :)
These are the most common everyday life of a developer. We wrote it once, then for months we finalize / cut it, we support it in general. Support is paid. All right.
If you want creativity, a flight of thought, the realization of all your knowledge - start your own startup and relax :)

Answer 2

There is a job, it is paid, what's the problem? This is a job, not a kindergarten.
Like/Dislike - this is the tenth thing.
Don't take long term work. Long Term just means supporting your work, and makes you do it in such a way that it doesn’t hurt to redo it later.
In general, long term work greatly corrects the brain, and very quickly weans writing shitty code that cannot be maintained.
Because when you realize that in order to change a button, you need to redo half of the project... it makes you think about the quality of your work.
It needs to be moved to a fairy tale. In reality, this happens in 0.00001% of cases. If the customer does not ask to redo something, it means that he is simply pressured by a toad to pay more. And the toad is stronger than the discomfort from the "imperfection".

Answer 3

Keep a changelog. In the case of cloudy conversations, you will have something to answer. In memory, such things are usually poorly stored.

Answer 4

In this case, clench your teeth. In general, it depends a lot on the situation, and I myself sometimes find myself in the role of you as a performer and in the role of RM, when the director is above me.
The directors stop only when the toad is choking, while there is no such thing, then they can play with the options as much as they want, until they get bored themselves and then return to the first one))

Answer 5

Raise the rate for finishing :) it will immediately become more pleasant to finish.
Any "popabol" should be compensated by payment.
In extreme cases, work on finishing touches is 2 times slower. ;)

Answer 6

Well, longterm projects they are all like that

Answer 7

common practice of developing NEW products for which there are no analogues.
It is not even your customer who decides how it will look and work in the end, but the market for which the product is adjusted, no one knows and cannot know what this final product should be, it is born in the way and feedback from consumers.

Answer 8

I work hourly and of course the whole thing is paid.
Therefore, there is no problem.
Of course, they pay me, but I don’t want to constantly redo it, I want to do it - turn it in - and leave for a new one,
Well, in vain. In a world of carefully crafted and well-paid things, fundamentally different approaches to development are used.
On the current project, we only laid the foundation for six months.
))))
And it's very interesting. Because there are sooooooooooooo different technologies than in fast projects.
and this is possible only if the customer has a clear understanding of all the wishes that the designer has implemented.

You yourself cannot foresee ahead (yes, yes, there are such development methods when even serious project changes do not require a complete redesign of the project, but you don’t use them), but you demand this from the customer.
In general, your demand makes you a very bad performer.
The customer achieves perfection by constantly bringing the project to perfection.
And you wanted to interfere with him.
It's okay if they don't pay. But they do pay.