How do you support product development if every customer is allowed to change the code?

How do you deal with this?

Is it OK to let the client change the software as often as he wants? I work in an environment where there are no specifications and constant change requests.

For each new customer, we must create a new branch and make so many changes that by the time I finish, I have a completely different product. Because of this, I greatly lose interest in programming.

So, I am not right to say that the customer should not be allowed to change the software at his request?

English is my second language, so please excuse any mistake.

Related:
How to deal with poorly informed customer choices

+3
source share
5 answers

EDIT : I initially skipped the part where you have a lot of clients, and sets up for each individual piece of software. I leave my original answer for reference, but it does not apply to this particular situation.

, . , , , , . , "" . , . , . , "" , , .

, - UserVoice, ( ) . , . , , . .

, , . , .

, . , .

, . , .

, , , . . , . , , . , .

-, . "" , ---. , , , , TDD, , .., , .

-, . , . , , . , , , , . , . , .

-, , . . , , , , , , , .

, , . - ( , ) , . , , . , , , .

, , . , , , , , . , , , , . , , . , , , .

+2

, ?

? ?

, -, , . , . , , , . , , , .

, , . , - .

+2

( ), . , UI - , , .

, , , , , . , , . .

, . , : P , . ( fogbugz , ). , tleat .

+1

.

.

0

, , , , . , , , , ( ).

a:

, , - .

I asked the manager how they avoid the hell version - given that they must support a specific version for each client. he said: "We do not, everyone gets the same version." they simply support one version for all clients, but disable features specific to the client.

  • LM
0
source

Source: https://habr.com/ru/post/1709022/


All Articles